Packet duplication control

ABSTRACT

A wireless device receives parameters indicating that first bearer(s) of bearer(s) are configured with duplication. Each bearer in bearer(s) is identified by an identifier. A control element of a fixed size of one octet is received. The control element comprises a sequence of activation bits comprising a first activation bit for a first bearer in the first bearer(s). A first position of the first activation bit in the one octet identifies a second position of a first bearer identifier in an ordered list of the bearer identifiers. A first value of the first activation bit indicates whether the PDCP duplication for the first bearer is activated or deactivated. In response to the control element indicating that the PDCP duplication is activated for the first bearer, a first packet corresponding to the first bearer is transmitted via a first cell and a duplicate of the first packet via a second cell.

This application claims the benefit of U.S. Provisional Application No.62/520,251, filed Jun. 15, 2017, which is hereby incorporated byreference in its entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present inventionare described herein with reference to the drawings.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present invention.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers in a carrier group as per an aspect of anembodiment of the present invention.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present invention.

FIG. 4 is a block diagram of a base station and a wireless device as peran aspect of an embodiment of the present invention.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present invention.

FIG. 6 is an example diagram for a protocol structure withmulti-connectivity as per an aspect of an embodiment of the presentinvention.

FIG. 7 is an example diagram for a protocol structure with CA and DC asper an aspect of an embodiment of the present invention.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present invention.

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentinvention.

FIG. 10A and FIG. 10B are example diagrams for interfaces between a 5Gcore network (e.g. NGC) and base stations (e.g. gNB and eLTE eNB) as peran aspect of an embodiment of the present invention.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F areexample diagrams for architectures of tight interworking between 5G RAN(e.g. gNB) and LTE RAN (e.g. (e)LTE eNB) as per an aspect of anembodiment of the present invention.

FIG. 12A, FIG. 12B, and FIG. 12C are example diagrams for radio protocolstructures of tight interworking bearers as per an aspect of anembodiment of the present invention.

FIG. 13A and FIG. 13B are example diagrams for gNB deployment scenariosas per an aspect of an embodiment of the present invention.

FIG. 14 is an example diagram for functional split option examples ofthe centralized gNB deployment scenario as per an aspect of anembodiment of the present invention.

FIG. 15 is an example illustration of mapping of logical channels totransmission durations as per an aspect of an embodiment of the presentinvention.

FIG. 16 is an example illustration of PDCP duplication and logicalchannel mapping restrictions as per an aspect of an embodiment of thepresent invention.

FIG. 17 is an example illustration of PDCP duplication control MACcontrol element (MAC CE) format as per an aspect of an embodiment of thepresent invention.

FIG. 18 is an example illustration of PDCP duplication control MACcontrol element (MAC CE) format as per an aspect of an embodiment of thepresent invention.

FIG. 19 is an example illustration of PDCP duplication control MACcontrol element (MAC CE) format as per an aspect of an embodiment of thepresent invention.

FIG. 20 is an example illustration of PDCP duplication control MACcontrol element (MAC CE) format as per an aspect of an embodiment of thepresent invention.

FIG. 21 is an example illustration of PDCP duplication control MACcontrol element (MAC CE) format as per an aspect of an embodiment of thepresent invention.

FIG. 22 is an example illustration of PDCP duplication procedure andPDCP duplication control MAC control element (MAC CE) format as per anaspect of an embodiment of the present invention.

FIG. 23 is an example illustration of PDCP duplication procedure as peran aspect of an embodiment of the present invention.

FIG. 24 is an example illustration of PDCP duplication procedure as peran aspect of an embodiment of the present invention.

FIG. 25 is an example illustration of PDCP duplication procedure andlogical channel mapping restriction as per an aspect of an embodiment ofthe present invention.

FIG. 26 is an example illustration of PDCP duplication procedure andlogical channel mapping restriction as per an aspect of an embodiment ofthe present invention.

FIG. 27 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 28 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 29 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 30 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 31 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 32 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 33 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 34 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 35 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 36 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present invention enable operation of carrieraggregation. Embodiments of the technology disclosed herein may beemployed in the technical field of multicarrier communication systems.More particularly, the embodiments of the technology disclosed hereinmay relate to packet duplication in a multicarrier communication system.

The following Acronyms are used throughout the present disclosure:

ASIC application-specific integrated circuit

BPSK binary phase shift keying

CA carrier aggregation

CSI channel state information

CDMA code division multiple access

CSS common search space

CPLD complex programmable logic devices

CC component carrier

CP cyclic prefix

DL downlink

DCI downlink control information

DC dual connectivity

eMBB enhanced mobile broadband

EPC evolved packet core

E-UTRAN evolved-universal terrestrial radio access network

FPGA field programmable gate arrays

FDD frequency division multiplexing

HDL hardware description languages

HARQ hybrid automatic repeat request

IE information element

LTE long term evolution

MCG master cell group

MeNB master evolved node B

MIB master information block

MAC media access control

MAC media access control

MME mobility management entity

mMTC massive machine type communications

NAS non-access stratum

NR new radio

OFDM orthogonal frequency division multiplexing

PDCP packet data convergence protocol

PDU packet data unit

PHY physical

PDCCH physical downlink control channel

PHICH physical HARQ indicator channel

PUCCH physical uplink control channel

PUSCH physical uplink shared channel

PCell primary cell

PCell primary cell

PCC primary component carrier

PSCell primary secondary cell

pTAG primary timing advance group

QAM quadrature amplitude modulation

QPSK quadrature phase shift keying

RBG resource block groups

RLC radio link control

RRC radio resource control

RA random access

RB resource blocks

SCC secondary component carrier

SCell secondary cell

Scell secondary cells

SCG secondary cell group

SeNB secondary evolved node B

sTAGs secondary timing advance group

SDU service data unit

S-GW serving gateway

SRB signaling radio bearer

SC-OFDM single carrier-OFDM

SFN system frame number

SIB system information block

TAI tracking area identifier

TAT time alignment timer

TDD time division duplexing

TDMA time division multiple access

TA timing advance

TAG timing advance group

TTI transmission time intervalTB transport block

UL uplink

UE user equipment

URLLC ultra-reliable low-latency communications

VHDL VHSIC hardware description language

CU central unit

DU distributed unit

Fs-C Fs-control plane

Fs-U Fs-user plane

gNB next generation node B

NGC next generation core

NG CP next generation control plane core

NG-C NG-control plane

NG-U NG-user plane

NR new radio

NR MAC new radio MAC

NR PHY new radio physical

NR PDCP new radio PDCP

NR RLC new radio RLC

NR RRC new radio RRC

NSSAI network slice selection assistance information

PLMN public land mobile network

UPGW user plane gateway

Xn-C Xn-control plane

Xn-U Xn-user plane

Xx-C Xx-control plane

Xx-U Xx-user plane

Example embodiments of the invention may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but are not limited to: CDMA, OFDM,TDMA, Wavelet technologies, and/or the like. Hybrid transmissionmechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed.Various modulation schemes may be applied for signal transmission in thephysical layer. Examples of modulation schemes include, but are notlimited to: phase, amplitude, code, a combination of these, and/or thelike. An example radio transmission method may implement QAM using BPSK,QPSK, 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radiotransmission may be enhanced by dynamically or semi-dynamically changingthe modulation and coding scheme depending on transmission requirementsand radio conditions.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present invention. As illustrated in thisexample, arrow(s) in the diagram may depict a subcarrier in amulticarrier OFDM system. The OFDM system may use technology such asOFDM technology, DFTS-OFDM, SC-OFDM technology, or the like. Forexample, arrow 101 shows a subcarrier transmitting information symbols.FIG. 1 is for illustration purposes, and a typical multicarrier OFDMsystem may include more subcarriers in a carrier. For example, thenumber of subcarriers in a carrier may be in the range of 10 to 10,000subcarriers. FIG. 1 shows two guard bands 106 and 107 in a transmissionband. As illustrated in FIG. 1, guard band 106 is between subcarriers103 and subcarriers 104. The example set of subcarriers A 102 includessubcarriers 103 and subcarriers 104. FIG. 1 also illustrates an exampleset of subcarriers B 105. As illustrated, there is no guard band betweenany two subcarriers in the example set of subcarriers B 105. Carriers ina multicarrier OFDM communication system may be contiguous carriers,non-contiguous carriers, or a combination of both contiguous andnon-contiguous carriers.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers as per an aspect of an embodiment of the presentinvention. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 10 carriers. Carrier A 204and carrier B 205 may have the same or different timing structures.Although FIG. 2 shows two synchronized carriers, carrier A 204 andcarrier B 205 may or may not be synchronized with each other. Differentradio frame structures may be supported for FDD and TDD duplexmechanisms. FIG. 2 shows an example FDD frame timing. Downlink anduplink transmissions may be organized into radio frames 201. In thisexample, radio frame duration is 10 msec. Other frame durations, forexample, in the range of 1 to 100 msec may also be supported. In thisexample, each 10 ms radio frame 201 may be divided into ten equallysized subframes 202. Other subframe durations such as including 0.5msec, 1 msec, 2 msec, and 5 msec may also be supported. Subframe(s) mayconsist of two or more slots (e.g. slots 206 and 207). For the exampleof FDD, 10 subframes may be available for downlink transmission and 10subframes may be available for uplink transmissions in each 10 msinterval. Uplink and downlink transmissions may be separated in thefrequency domain. A slot may be 7 or 14 OFDM symbols for the samesubcarrier spacing of up to 60 kHz with normal CP. A slot may be 14 OFDMsymbols for the same subcarrier spacing higher than 60 kHz with normalCP. A slot may contain all downlink, all uplink, or a downlink part andan uplink part and/or alike. Slot aggregation may be supported, e.g.,data transmission may be scheduled to span one or multiple slots. In anexample, a mini-slot may start at an OFDM symbol in a subframe. Amini-slot may have a duration of one or more OFDM symbols. Slot(s) mayinclude a plurality of OFDM symbols 203. The number of OFDM symbols 203in a slot 206 may depend on the cyclic prefix length and subcarrierspacing.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present invention. The resource grid structure intime 304 and frequency 305 is illustrated in FIG. 3. The quantity ofdownlink subcarriers or RBs may depend, at least in part, on thedownlink transmission bandwidth 306 configured in the cell. The smallestradio resource unit may be called a resource element (e.g. 301).Resource elements may be grouped into resource blocks (e.g. 302).Resource blocks may be grouped into larger radio resources calledResource Block Groups (RBG) (e.g. 303). The transmitted signal in slot206 may be described by one or several resource grids of a plurality ofsubcarriers and a plurality of OFDM symbols. Resource blocks may be usedto describe the mapping of certain physical channels to resourceelements. Other pre-defined groupings of physical resource elements maybe implemented in the system depending on the radio technology. Forexample, 24 subcarriers may be grouped as a radio block for a durationof 5 msec. In an illustrative example, a resource block may correspondto one slot in the time domain and 180 kHz in the frequency domain (for15 KHz subcarrier bandwidth and 12 subcarriers).

In an example embodiment, multiple numerologies may be supported. In anexample, a numerology may be derived by scaling a basic subcarrierspacing by an integer N. In an example, scalable numerology may allow atleast from 15 kHz to 480 kHz subcarrier spacing. The numerology with 15kHz and scaled numerology with different subcarrier spacing with thesame CP overhead may align at a symbol boundary every 1 ms in a NRcarrier.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present invention. FIG. 5A shows an example uplink physical channel.The baseband signal representing the physical uplink shared channel mayperform the following processes. These functions are illustrated asexamples and it is anticipated that other mechanisms may be implementedin various embodiments. The functions may comprise scrambling,modulation of scrambled bits to generate complex-valued symbols, mappingof the complex-valued modulation symbols onto one or severaltransmission layers, transform precoding to generate complex-valuedsymbols, precoding of the complex-valued symbols, mapping of precodedcomplex-valued symbols to resource elements, generation ofcomplex-valued time-domain DFTS-OFDM/SC-FDMA signal for each antennaport, and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued DFTS-OFDM/SC-FDMA baseband signal for each antenna portand/or the complex-valued PRACH baseband signal is shown in FIG. 5B.Filtering may be employed prior to transmission.

An example structure for Downlink Transmissions is shown in FIG. 5C. Thebaseband signal representing a downlink physical channel may perform thefollowing processes. These functions are illustrated as examples and itis anticipated that other mechanisms may be implemented in variousembodiments. The functions include scrambling of coded bits in each ofthe codewords to be transmitted on a physical channel; modulation ofscrambled bits to generate complex-valued modulation symbols; mapping ofthe complex-valued modulation symbols onto one or several transmissionlayers; precoding of the complex-valued modulation symbols on each layerfor transmission on the antenna ports; mapping of complex-valuedmodulation symbols for each antenna port to resource elements;generation of complex-valued time-domain OFDM signal for each antennaport, and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for each antenna port is shown inFIG. 5D. Filtering may be employed prior to transmission.

FIG. 4 is an example block diagram of a base station 401 and a wirelessdevice 406, as per an aspect of an embodiment of the present invention.A communication network 400 may include at least one base station 401and at least one wireless device 406. The base station 401 may includeat least one communication interface 402, at least one processor 403,and at least one set of program code instructions 405 stored innon-transitory memory 404 and executable by the at least one processor403. The wireless device 406 may include at least one communicationinterface 407, at least one processor 408, and at least one set ofprogram code instructions 410 stored in non-transitory memory 409 andexecutable by the at least one processor 408. Communication interface402 in base station 401 may be configured to engage in communicationwith communication interface 407 in wireless device 406 via acommunication path that includes at least one wireless link 411.Wireless link 411 may be a bi-directional link. Communication interface407 in wireless device 406 may also be configured to engage in acommunication with communication interface 402 in base station 401. Basestation 401 and wireless device 406 may be configured to send andreceive data over wireless link 411 using multiple frequency carriers.According to some of the various aspects of embodiments, transceiver(s)may be employed. A transceiver is a device that includes both atransmitter and receiver. Transceivers may be employed in devices suchas wireless devices, base stations, relay nodes, and/or the like.Example embodiments for radio technology implemented in communicationinterface 402, 407 and wireless link 411 are illustrated are FIG. 1,FIG. 2, FIG. 3, FIG. 5, and associated text.

An interface may be a hardware interface, a firmware interface, asoftware interface, and/or a combination thereof. The hardware interfacemay include connectors, wires, electronic devices such as drivers,amplifiers, and/or the like. A software interface may include codestored in a memory device to implement protocol(s), protocol layers,communication drivers, device drivers, combinations thereof, and/or thelike. A firmware interface may include a combination of embeddedhardware and code stored in and/or in communication with a memory deviceto implement connections, electronic device operations, protocol(s),protocol layers, communication drivers, device drivers, hardwareoperations, combinations thereof, and/or the like.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics inthe device, whether the device is in an operational or non-operationalstate.

According to some of the various aspects of embodiments, a 5G networkmay include a multitude of base stations, providing a user plane NRPDCP/NR RLC/NR MAC/NR PHY and control plane (NR RRC) protocolterminations towards the wireless device. The base station(s) may beinterconnected with other base station(s) (e.g. employing an Xninterface). The base stations may also be connected employing, forexample, an NG interface to an NGC. FIG. 10A and FIG. 10B are examplediagrams for interfaces between a 5G core network (e.g. NGC) and basestations (e.g. gNB and eLTE eNB) as per an aspect of an embodiment ofthe present invention. For example, the base stations may beinterconnected to the NGC control plane (e.g. NG CP) employing the NG-Cinterface and to the NGC user plane (e.g. UPGW) employing the NG-Uinterface. The NG interface may support a many-to-many relation between5G core networks and base stations.

A base station may include many sectors for example: 1, 2, 3, 4, or 6sectors. A base station may include many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At RRC connectionestablishment/re-establishment/handover, one serving cell may providethe NAS (non-access stratum) mobility information (e.g. TAI), and at RRCconnection re-establishment/handover, one serving cell may provide thesecurity input. This cell may be referred to as the Primary Cell(PCell). In the downlink, the carrier corresponding to the PCell may bethe Downlink Primary Component Carrier (DL PCC), while in the uplink, itmay be the Uplink Primary Component Carrier (UL PCC). Depending onwireless device capabilities, Secondary Cells (SCells) may be configuredto form together with the PCell a set of serving cells. In the downlink,the carrier corresponding to an SCell may be a Downlink SecondaryComponent Carrier (DL SCC), while in the uplink, it may be an UplinkSecondary Component Carrier (UL SCC). An SCell may or may not have anuplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to only one cell. The cell ID or Cell index mayalso identify the downlink carrier or uplink carrier of the cell(depending on the context it is used). In the specification, cell ID maybe equally referred to a carrier ID, and cell index may be referred tocarrier index. In implementation, the physical cell ID or cell index maybe assigned to a cell. A cell ID may be determined using asynchronization signal transmitted on a downlink carrier. A cell indexmay be determined using RRC messages. For example, when thespecification refers to a first physical cell ID for a first downlinkcarrier, the specification may mean the first physical cell ID is for acell comprising the first downlink carrier. The same concept may applyto, for example, carrier activation. When the specification indicatesthat a first carrier is activated, the specification may equally meanthat the cell comprising the first carrier is activated.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, traffic load, initial systemset up, packet sizes, traffic characteristics, a combination of theabove, and/or the like. When the one or more criteria are met, variousexample embodiments may be applied. Therefore, it may be possible toimplement example embodiments that selectively implement disclosedprotocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices may support multiple technologies, and/or multiple releases ofthe same technology. Wireless devices may have some specificcapability(ies) depending on its wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE or 5G releasewith a given capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of wireless devices in a coveragearea that may not comply with the disclosed methods, for example,because those wireless devices perform based on older releases of LTE or5G technology.

FIG. 6 and FIG. 7 are example diagrams for protocol structure with CAand multi-connectivity as per an aspect of an embodiment of the presentinvention. NR may support multi-connectivity operation whereby amultiple RX/TX UE in RRC_CONNECTED may be configured to utilize radioresources provided by multiple schedulers located in multiple gNBsconnected via a non-ideal or ideal backhaul over the Xn interface. gNBsinvolved in multi-connectivity for a certain UE may assume two differentroles: a gNB may either act as a master gNB or as a secondary gNB. Inmulti-connectivity, a UE may be connected to one master gNB and one ormore secondary gNBs. FIG. 7 illustrates one example structure for the UEside MAC entities when a Master Cell Group (MCG) and a Secondary CellGroup (SCG) are configured, and it may not restrict implementation.Media Broadcast Multicast Service (MBMS) reception is not shown in thisfigure for simplicity.

In multi-connectivity, the radio protocol architecture that a particularbearer uses may depend on how the bearer is setup. Three alternativesmay exist, an MCG bearer, an SCG bearer and a split bearer as shown inFIG. 6. NR RRC may be located in master gNB and SRBs may be configuredas a MCG bearer type and may use the radio resources of the master gNB.Multi-connectivity may also be described as having at least one bearerconfigured to use radio resources provided by the secondary gNB.Multi-connectivity may or may not be configured/implemented in exampleembodiments of the invention.

In the case of multi-connectivity, the UE may be configured withmultiple NR MAC entities: one NR MAC entity for master gNB, and other NRMAC entities for secondary gNBs. In multi-connectivity, the configuredset of serving cells for a UE may comprise of two subsets: the MasterCell Group (MCG) containing the serving cells of the master gNB, and theSecondary Cell Groups (SCGs) containing the serving cells of thesecondary gNBs. For a SCG, one or more of the following may be applied:at least one cell in the SCG has a configured UL CC and one of them,named PSCell (or PCell of SCG, or sometimes called PCell), is configuredwith PUCCH resources; when the SCG is configured, there may be at leastone SCG bearer or one Split bearer; upon detection of a physical layerproblem or a random access problem on a PSCell, or the maximum number ofNR RLC retransmissions has been reached associated with the SCG, or upondetection of an access problem on a PSCell during a SCG addition or aSCG change: a RRC connection re-establishment procedure may not betriggered, UL transmissions towards cells of the SCG are stopped, amaster gNB may be informed by the UE of a SCG failure type, for splitbearer, the DL data transfer over the master gNB is maintained; the NRRLC AM bearer may be configured for the split bearer; like PCell, PSCellmay not be de-activated; PSCell may be changed with a SCG change (e.g.with security key change and a RACH procedure); and/or a direct bearertype change between a Split bearer and a SCG bearer or simultaneousconfiguration of a SCG and a Split bearer may or may not supported.

With respect to the interaction between a master gNB and secondary gNBsfor multi-connectivity, one or more of the following principles may beapplied: the master gNB may maintain the RRM measurement configurationof the UE and may, (e.g, based on received measurement reports ortraffic conditions or bearer types), decide to ask a secondary gNB toprovide additional resources (serving cells) for a UE; upon receiving arequest from the master gNB, a secondary gNB may create a container thatmay result in the configuration of additional serving cells for the UE(or decide that it has no resource available to do so); for UEcapability coordination, the master gNB may provide (part of) the ASconfiguration and the UE capabilities to the secondary gNB; the mastergNB and the secondary gNB may exchange information about a UEconfiguration by employing of NR RRC containers (inter-node messages)carried in Xn messages; the secondary gNB may initiate a reconfigurationof its existing serving cells (e.g., PUCCH towards the secondary gNB);the secondary gNB may decide which cell is the PSCell within the SCG;the master gNB may or may not change the content of the NR RRCconfiguration provided by the secondary gNB; in the case of a SCGaddition and a SCG SCell addition, the master gNB may provide the latestmeasurement results for the SCG cell(s); both a master gNB and secondarygNBs may know the SFN and subframe offset of each other by OAM, (e.g.,for the purpose of DRX alignment and identification of a measurementgap). In an example, when adding a new SCG SCell, dedicated NR RRCsignaling may be used for sending required system information of thecell as for CA, except for the SFN acquired from a MIB of the PSCell ofa SCG.

In an example, serving cells may be grouped in a TA group (TAG). Servingcells in one TAG may use the same timing reference. For a given TAG,user equipment (UE) may use at least one downlink carrier as a timingreference. For a given TAG, a UE may synchronize uplink subframe andframe transmission timing of uplink carriers belonging to the same TAG.In an example, serving cells having an uplink to which the same TAapplies may correspond to serving cells hosted by the same receiver. AUE supporting multiple TAs may support two or more TA groups. One TAgroup may contain the PCell and may be called a primary TAG (pTAG). In amultiple TAG configuration, at least one TA group may not contain thePCell and may be called a secondary TAG (sTAG). In an example, carrierswithin the same TA group may use the same TA value and/or the sametiming reference. When DC is configured, cells belonging to a cell group(MCG or SCG) may be grouped into multiple TAGs including a pTAG and oneor more sTAGs.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present invention. In Example 1, pTAG comprises PCell,and an sTAG comprises SCell1. In Example 2, a pTAG comprises a PCell andSCell1, and an sTAG comprises SCell2 and SCell3. In Example 3, pTAGcomprises PCell and SCell1, and an sTAG1 includes SCell2 and SCell3, andsTAG2 comprises SCell4. Up to four TAGs may be supported in a cell group(MCG or SCG) and other example TAG configurations may also be provided.In various examples in this disclosure, example mechanisms are describedfor a pTAG and an sTAG. Some of the example mechanisms may be applied toconfigurations with multiple sTAGs.

In an example, an eNB may initiate an RA procedure via a PDCCH order foran activated SCell. This PDCCH order may be sent on a scheduling cell ofthis SCell. When cross carrier scheduling is configured for a cell, thescheduling cell may be different than the cell that is employed forpreamble transmission, and the PDCCH order may include an SCell index.At least a non-contention based RA procedure may be supported forSCell(s) assigned to sTAG(s).

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentinvention. An eNB transmits an activation command 600 to activate anSCell. A preamble 602 (Msg1) may be sent by a UE in response to a PDCCHorder 601 on an SCell belonging to an sTAG. In an example embodiment,preamble transmission for SCells may be controlled by the network usingPDCCH format 1A. Msg2 message 603 (RAR: random access response) inresponse to the preamble transmission on the SCell may be addressed toRA-RNTI in a PCell common search space (CSS). Uplink packets 604 may betransmitted on the SCell in which the preamble was transmitted.

According to some of the various aspects of embodiments, initial timingalignment may be achieved through a random access procedure. This mayinvolve a UE transmitting a random access preamble and an eNB respondingwith an initial TA command NTA (amount of timing advance) within arandom access response window. The start of the random access preamblemay be aligned with the start of a corresponding uplink subframe at theUE assuming NTA=0. The eNB may estimate the uplink timing from therandom access preamble transmitted by the UE. The TA command may bederived by the eNB based on the estimation of the difference between thedesired UL timing and the actual UL timing. The UE may determine theinitial uplink transmission timing relative to the correspondingdownlink of the sTAG on which the preamble is transmitted.

The mapping of a serving cell to a TAG may be configured by a servingeNB with RRC signaling. The mechanism for TAG configuration andreconfiguration may be based on RRC signaling. According to some of thevarious aspects of embodiments, when an eNB performs an SCell additionconfiguration, the related TAG configuration may be configured for theSCell. In an example embodiment, an eNB may modify the TAG configurationof an SCell by removing (releasing) the SCell and adding(configuring) anew SCell (with the same physical cell ID and frequency) with an updatedTAG ID. The new SCell with the updated TAG ID may initially be inactivesubsequent to being assigned the updated TAG ID. The eNB may activatethe updated new SCell and start scheduling packets on the activatedSCell. In an example implementation, it may not be possible to changethe TAG associated with an SCell, but rather, the SCell may need to beremoved and a new SCell may need to be added with another TAG. Forexample, if there is a need to move an SCell from an sTAG to a pTAG, atleast one RRC message, for example, at least one RRC reconfigurationmessage, may be send to the UE to reconfigure TAG configurations byreleasing the SCell and then configuring the SCell as a part of the pTAG(when an SCell is added/configured without a TAG index, the SCell may beexplicitly assigned to the pTAG). The PCell may not change its TA groupand may be a member of the pTAG.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g. to establish, modify and/or release RBs,to perform handover, to setup, modify, and/or release measurements, toadd, modify, and/or release SCells). If the received RRC ConnectionReconfiguration message includes the sCellToReleaseList, the UE mayperform an SCell release. If the received RRC Connection Reconfigurationmessage includes the sCellToAddModList, the UE may perform SCelladditions or modification.

In LTE Release-10 and Release-11 CA, a PUCCH is only transmitted on thePCell (PSCell) to an eNB. In LTE-Release 12 and earlier, a UE maytransmit PUCCH information on one cell (PCell or PSCell) to a given eNB.

As the number of CA capable UEs and also the number of aggregatedcarriers increase, the number of PUCCHs and also the PUCCH payload sizemay increase. Accommodating the PUCCH transmissions on the PCell maylead to a high PUCCH load on the PCell. A PUCCH on an SCell may beintroduced to offload the PUCCH resource from the PCell. More than onePUCCH may be configured for example, a PUCCH on a PCell and anotherPUCCH on an SCell. In the example embodiments, one, two or more cellsmay be configured with PUCCH resources for transmitting CSI/ACK/NACK toa base station. Cells may be grouped into multiple PUCCH groups, and oneor more cell within a group may be configured with a PUCCH. In anexample configuration, one SCell may belong to one PUCCH group. SCellswith a configured PUCCH transmitted to a base station may be called aPUCCH SCell, and a cell group with a common PUCCH resource transmittedto the same base station may be called a PUCCH group.

In an example embodiment, a MAC entity may have a configurable timertimeAlignmentTimer per TAG. The timeAlignmentTimer may be used tocontrol how long the MAC entity considers the Serving Cells belonging tothe associated TAG to be uplink time aligned. The MAC entity may, when aTiming Advance Command MAC control element is received, apply the TimingAdvance Command for the indicated TAG; start or restart thetimeAlignmentTimer associated with the indicated TAG. The MAC entitymay, when a Timing Advance Command is received in a Random AccessResponse message for a serving cell belonging to a TAG and/or if theRandom Access Preamble was not selected by the MAC entity, apply theTiming Advance Command for this TAG and start or restart thetimeAlignmentTimer associated with this TAG. Otherwise, if thetimeAlignmentTimer associated with this TAG is not running, the TimingAdvance Command for this TAG may be applied and the timeAlignmentTimerassociated with this TAG started. When the contention resolution isconsidered not successful, a timeAlignmentTimer associated with this TAGmay be stopped. Otherwise, the MAC entity may ignore the received TimingAdvance Command.

In example embodiments, a timer is running once it is started, until itis stopped or until it expires; otherwise it may not be running. A timercan be started if it is not running or restarted if it is running. Forexample, a timer may be started or restarted from its initial value.

Example embodiments of the invention may enable operation ofmulti-carrier communications. Other example embodiments may comprise anon-transitory tangible computer readable media comprising instructionsexecutable by one or more processors to cause operation of multi-carriercommunications. Yet other example embodiments may comprise an article ofmanufacture that comprises a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g. wirelesscommunicator, UE, base station, etc.) to enable operation ofmulti-carrier communications. The device may include processors, memory,interfaces, and/or the like. Other example embodiments may comprisecommunication networks comprising devices such as base stations,wireless devices (or user equipment: UE), servers, switches, antennas,and/or the like.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F areexample diagrams for architectures of tight interworking between 5G RANand LTE RAN as per an aspect of an embodiment of the present invention.The tight interworking may enable a multiple RX/TX UE in RRC_CONNECTEDto be configured to utilize radio resources provided by two schedulerslocated in two base stations (e.g. (e)LTE eNB and gNB) connected via anon-ideal or ideal backhaul over the Xx interface between LTE eNB andgNB or the Xn interface between eLTE eNB and gNB. Base stations involvedin tight interworking for a certain UE may assume two different roles: abase station may either act as a master base station or as a secondarybase station. In tight interworking, a UE may be connected to one masterbase station and one secondary base station. Mechanisms implemented intight interworking may be extended to cover more than two base stations.

In FIG. 11A and FIG. 11B, a master base station may be an LTE eNB, whichmay be connected to EPC nodes (e.g. to an MME via the S1-C interface andto an S-GW via the S1-U interface), and a secondary base station may bea gNB, which may be a non-standalone node having a control planeconnection via an Xx-C interface to an LTE eNB. In the tightinterworking architecture of FIG. 11A, a user plane for a gNB may beconnected to an S-GW through an LTE eNB via an Xx-U interface betweenLTE eNB and gNB and an S1-U interface between LTE eNB and S-GW. In thearchitecture of FIG. 11B, a user plane for a gNB may be connecteddirectly to an S-GW via an S1-U interface between gNB and S-GW.

In FIG. 11C and FIG. 11D, a master base station may be a gNB, which maybe connected to NGC nodes (e.g. to a control plane core node via theNG-C interface and to a user plane core node via the NG-U interface),and a secondary base station may be an eLTE eNB, which may be anon-standalone node having a control plane connection via an Xn-Cinterface to a gNB. In the tight interworking architecture of FIG. 11C,a user plane for an eLTE eNB may be connected to a user plane core nodethrough a gNB via an Xn-U interface between eLTE eNB and gNB and an NG-Uinterface between gNB and user plane core node. In the architecture ofFIG. 11D, a user plane for an eLTE eNB may be connected directly to auser plane core node via an NG-U interface between eLTE eNB and userplane core node.

In FIG. 11E and FIG. 11F, a master base station may be an eLTE eNB,which may be connected to NGC nodes (e.g. to a control plane core nodevia the NG-C interface and to a user plane core node via the NG-Uinterface), and a secondary base station may be a gNB, which may be anon-standalone node having a control plane connection via an Xn-Cinterface to an eLTE eNB. In the tight interworking architecture of FIG.11E, a user plane for a gNB may be connected to a user plane core nodethrough an eLTE eNB via an Xn-U interface between eLTE eNB and gNB andan NG-U interface between eLTE eNB and user plane core node. In thearchitecture of FIG. 11F, a user plane for a gNB may be connecteddirectly to a user plane core node via an NG-U interface between gNB anduser plane core node.

FIG. 12A, FIG. 12B, and FIG. 12C are example diagrams for radio protocolstructures of tight interworking bearers as per an aspect of anembodiment of the present invention. In FIG. 12A, an LTE eNB may be amaster base station, and a gNB may be a secondary base station. In FIG.12B, a gNB may be a master base station, and an eLTE eNB may be asecondary base station. In FIG. 12C, an eLTE eNB may be a master basestation, and a gNB may be a secondary base station. In 5G network, theradio protocol architecture that a particular bearer uses may depend onhow the bearer is setup. Three alternatives may exist, an MCG bearer, anSCG bearer, and a split bearer as shown in FIG. 12A, FIG. 12B, and FIG.12C. NR RRC may be located in master base station, and SRBs may beconfigured as an MCG bearer type and may use the radio resources of themaster base station. Tight interworking may also be described as havingat least one bearer configured to use radio resources provided by thesecondary base station. Tight interworking may or may not beconfigured/implemented in example embodiments of the invention.

In the case of tight interworking, the UE may be configured with two MACentities: one MAC entity for master base station, and one MAC entity forsecondary base station. In tight interworking, the configured set ofserving cells for a UE may comprise of two subsets: the Master CellGroup (MCG) containing the serving cells of the master base station, andthe Secondary Cell Group (SCG) containing the serving cells of thesecondary base station. For a SCG, one or more of the following may beapplied: at least one cell in the SCG has a configured UL CC and one ofthem, named PSCell (or PCell of SCG, or sometimes called PCell), isconfigured with PUCCH resources; when the SCG is configured, there maybe at least one SCG bearer or one split bearer; upon detection of aphysical layer problem or a random access problem on a PSCell, or themaximum number of (NR) RLC retransmissions has been reached associatedwith the SCG, or upon detection of an access problem on a PSCell duringa SCG addition or a SCG change: a RRC connection re-establishmentprocedure may not be triggered, UL transmissions towards cells of theSCG are stopped, a master base station may be informed by the UE of aSCG failure type, for split bearer, the DL data transfer over the masterbase station is maintained; the RLC AM bearer may be configured for thesplit bearer; like PCell, PSCell may not be de-activated; PSCell may bechanged with a SCG change (e.g. with security key change and a RACHprocedure); and/or neither a direct bearer type change between a Splitbearer and a SCG bearer nor simultaneous configuration of a SCG and aSplit bearer are supported.

With respect to the interaction between a master base station and asecondary base station, one or more of the following principles may beapplied: the master base station may maintain the RRM measurementconfiguration of the UE and may, (e.g, based on received measurementreports, traffic conditions, or bearer types), decide to ask a secondarybase station to provide additional resources (serving cells) for a UE;upon receiving a request from the master base station, a secondary basestation may create a container that may result in the configuration ofadditional serving cells for the UE (or decide that it has no resourceavailable to do so); for UE capability coordination, the master basestation may provide (part of) the AS configuration and the UEcapabilities to the secondary base station; the master base station andthe secondary base station may exchange information about a UEconfiguration by employing of RRC containers (inter-node messages)carried in Xn or Xx messages; the secondary base station may initiate areconfiguration of its existing serving cells (e.g., PUCCH towards thesecondary base station); the secondary base station may decide whichcell is the PSCell within the SCG; the master base station may notchange the content of the RRC configuration provided by the secondarybase station; in the case of a SCG addition and a SCG SCell addition,the master base station may provide the latest measurement results forthe SCG cell(s); both a master base station and a secondary base stationmay know the SFN and subframe offset of each other by OAM, (e.g., forthe purpose of DRX alignment and identification of a measurement gap).In an example, when adding a new SCG SCell, dedicated RRC signaling maybe used for sending required system information of the cell as for CA,except for the SFN acquired from a MIB of the PSCell of a SCG.

FIG. 13A and FIG. 13B are example diagrams for gNB deployment scenariosas per an aspect of an embodiment of the present invention. In thenon-centralized deployment scenario in FIG. 13A, the full protocol stack(e.g. NR RRC, NR PDCP, NR RLC, NR MAC, and NR PHY) may be supported atone node. In the centralized deployment scenario in FIG. 13B, upperlayers of gNB may be located in a Central Unit (CU), and lower layers ofgNB may be located in Distributed Units (DU). The CU-DU interface (e.g.Fs interface) connecting CU and DU may be ideal or non-ideal. Fs-C mayprovide a control plane connection over Fs interface, and Fs-U mayprovide a user plane connection over Fs interface. In the centralizeddeployment, different functional split options between CU and DUs may bepossible by locating different protocol layers (RAN functions) in CU andDU. The functional split may support flexibility to move RAN functionsbetween CU and DU depending on service requirements and/or networkenvironments. The functional split option may change during operationafter Fs interface setup procedure, or may change only in Fs setupprocedure (i.e. static during operation after Fs setup procedure).

FIG. 14 is an example diagram for different functional split optionexamples of the centralized gNB deployment scenario as per an aspect ofan embodiment of the present invention. In the split option example 1,an NR RRC may be in CU, and NR PDCP, NR RLC, NR MAC, NR PHY, and RF maybe in DU. In the split option example 2, an NR RRC and NR PDCP may be inCU, and NR RLC, NR MAC, NR PHY, and RF may be in DU. In the split optionexample 3, an NR RRC, NR PDCP, and partial function of NR RLC may be inCU, and the other partial function of NR RLC, NR MAC, NR PHY, and RF maybe in DU. In the split option example 4, an NR RRC, NR PDCP, and NR RLCmay be in CU, and NR MAC, NR PHY, and RF may be in DU. In the splitoption example 5, an NR RRC, NR PDCP, NR RLC, and partial function of NRMAC may be in CU, and the other partial function of NR MAC, NR PHY, andRF may be in DU. In the split option example 6, an NR RRC, NR PDCP, NRRLC, and NR MAC may be in CU, and NR PHY and RF may be in DU. In thesplit option example 7, an NR RRC, NR PDCP, NR RLC, NR MAC, and partialfunction of NR PHY may be in CU, and the other partial function of NRPHY and RF may be in DU. In the split option example 8, an NR RRC, NRPDCP, NR RLC, NR MAC, and NR PHY may be in CU, and RF may be in DU.

The functional split may be configured per CU, per DU, per UE, perbearer, per slice, or with other granularities. In per CU split, a CUmay have a fixed split, and DUs may be configured to match the splitoption of CU. In per DU split, each DU may be configured with adifferent split, and a CU may provide different split options fordifferent DUs. In per UE split, a gNB (CU and DU) may provide differentsplit options for different UEs. In per bearer split, different splitoptions may be utilized for different bearer types. In per slice splice,different split options may be applied for different slices.

In an example embodiment, the new radio access network (new RAN) maysupport different network slices, which may allow differentiatedtreatment customized to support different service requirements with endto end scope. The new RAN may provide a differentiated handling oftraffic for different network slices that may be pre-configured, and mayallow a single RAN node to support multiple slices. The new RAN maysupport selection of a RAN part for a given network slice, by one ormore slice ID(s) or NSSAI(s) provided by a UE or a NGC (e.g. NG CP). Theslice ID(s) or NSSAI(s) may identify one or more of pre-configurednetwork slices in a PLMN. For initial attach, a UE may provide a sliceID and/or an NSSAI, and a RAN node (e.g. gNB) may use the slice ID orthe NSSAI for routing an initial NAS signaling to an NGC control planefunction (e.g. NG CP). If a UE does not provide any slice ID or NSSAI, aRAN node may send a NAS signaling to a default NGC control planefunction. For subsequent accesses, the UE may provide a temporary ID fora slice identification, which may be assigned by the NGC control planefunction, to enable a RAN node to route the NAS message to a relevantNGC control plane function. The new RAN may support resource isolationbetween slices. The RAN resource isolation may be achieved by avoidingthat shortage of shared resources in one slice breaks a service levelagreement for another slice.

The amount of data traffic carried over cellular networks is expected toincrease for many years to come. The number of users/devices isincreasing and each user/device accesses an increasing number andvariety of services, e.g. video delivery, large files, images. Thisrequires not only high capacity in the network, but also provisioningvery high data rates to meet customers' expectations on interactivityand responsiveness. More spectrum is therefore needed for cellularoperators to meet the increasing demand. Considering user expectationsof high data rates along with seamless mobility, it is beneficial thatmore spectrum be made available for deploying macro cells as well assmall cells for cellular systems.

Striving to meet the market demands, there has been increasing interestfrom operators in deploying some complementary access utilizingunlicensed spectrum to meet the traffic growth. This is exemplified bythe large number of operator-deployed Wi-Fi networks and the 3GPPstandardization of LTE/WLAN interworking solutions. This interestindicates that unlicensed spectrum, when present, can be an effectivecomplement to licensed spectrum for cellular operators to helpaddressing the traffic explosion in some scenarios, such as hotspotareas. LAA offers an alternative for operators to make use of unlicensedspectrum while managing one radio network, thus offering newpossibilities for optimizing the network's efficiency.

In an example embodiment, Listen-before-talk (clear channel assessment)may be implemented for transmission in an LAA cell. In alisten-before-talk (LBT) procedure, equipment may apply a clear channelassessment (CCA) check before using the channel. For example, the CCAutilizes at least energy detection to determine the presence or absenceof other signals on a channel in order to determine if a channel isoccupied or clear, respectively. For example, European and Japaneseregulations mandate the usage of LBT in the unlicensed bands. Apart fromregulatory requirements, carrier sensing via LBT may be one way for fairsharing of the unlicensed spectrum.

In an example embodiment, discontinuous transmission on an unlicensedcarrier with limited maximum transmission duration may be enabled. Someof these functions may be supported by one or more signals to betransmitted from the beginning of a discontinuous LAA downlinktransmission. Channel reservation may be enabled by the transmission ofsignals, by an LAA node, after gaining channel access via a successfulLBT operation, so that other nodes that receive the transmitted signalwith energy above a certain threshold sense the channel to be occupied.Functions that may need to be supported by one or more signals for LAAoperation with discontinuous downlink transmission may include one ormore of the following: detection of the LAA downlink transmission(including cell identification) by UEs; time & frequency synchronizationof UEs.

In an example embodiment, DL LAA design may employ subframe boundaryalignment according to LTE-A carrier aggregation timing relationshipsacross serving cells aggregated by CA. This may not imply that the eNBtransmissions can start only at the subframe boundary. LAA may supporttransmitting PDSCH when not all OFDM symbols are available fortransmission in a subframe according to LBT. Delivery of necessarycontrol information for the PDSCH may also be supported.

LBT procedure may be employed for fair and friendly coexistence of LAAwith other operators and technologies operating in unlicensed spectrum.LBT procedures on a node attempting to transmit on a carrier inunlicensed spectrum require the node to perform a clear channelassessment to determine if the channel is free for use. An LBT proceduremay involve at least energy detection to determine if the channel isbeing used. For example, regulatory requirements in some regions, e.g.,in Europe, specify an energy detection threshold such that if a nodereceives energy greater than this threshold, the node assumes that thechannel is not free. While nodes may follow such regulatoryrequirements, a node may optionally use a lower threshold for energydetection than that specified by regulatory requirements. In an example,LAA may employ a mechanism to adaptively change the energy detectionthreshold, e.g., LAA may employ a mechanism to adaptively lower theenergy detection threshold from an upper bound. Adaptation mechanism maynot preclude static or semi-static setting of the threshold. In anexample Category 4 LBT mechanism or other type of LBT mechanisms may beimplemented.

Various example LBT mechanisms may be implemented. In an example, forsome signals, in some implementation scenarios, in some situations,and/or in some frequencies no LBT procedure may performed by thetransmitting entity. In an example, Category 2 (e.g. LBT without randomback-off) may be implemented. The duration of time that the channel issensed to be idle before the transmitting entity transmits may bedeterministic. In an example, Category 3 (e.g. LBT with random back-offwith a contention window of fixed size) may be implemented. The LBTprocedure may have the following procedure as one of its components. Thetransmitting entity may draw a random number N within a contentionwindow. The size of the contention window may be specified by theminimum and maximum value of N. The size of the contention window may befixed. The random number N may be employed in the LBT procedure todetermine the duration of time that the channel is sensed to be idlebefore the transmitting entity transmits on the channel. In an example,Category 4 (e.g. LBT with random back-off with a contention window ofvariable size) may be implemented. The transmitting entity may draw arandom number N within a contention window. The size of contentionwindow may be specified by the minimum and maximum value of N. Thetransmitting entity may vary the size of the contention window whendrawing the random number N. The random number N is used in the LBTprocedure to determine the duration of time that the channel is sensedto be idle before the transmitting entity transmits on the channel.

LAA may employ uplink LBT at the UE. The UL LBT scheme may be differentfrom the DL LBT scheme (e.g. by using different LBT mechanisms orparameters) for example, since the LAA UL is based on scheduled accesswhich affects a UE's channel contention opportunities. Otherconsiderations motivating a different UL LBT scheme include, but are notlimited to, multiplexing of multiple UEs in a single subframe.

In an example, a DL transmission burst may be a continuous transmissionfrom a DL transmitting node with no transmission immediately before orafter from the same node on the same CC. An UL transmission burst from aUE perspective may be a continuous transmission from a UE with notransmission immediately before or after from the same UE on the sameCC. In an example, UL transmission burst is defined from a UEperspective. In an example, an UL transmission burst may be defined froman eNB perspective. In an example, in case of an eNB operating DL+UL LAAover the same unlicensed carrier, DL transmission burst(s) and ULtransmission burst(s) on LAA may be scheduled in a TDM manner over thesame unlicensed carrier. For example, an instant in time may be part ofa DL transmission burst or an UL transmission burst.

Transmission reliability and latency enhancement are example aspects ofultra-reliable low-latency communications (URLLC). In an example,multi-connectivity may enhance reliability for URLLC. In an example,multi-connectivity may comprise packet duplication, link selection, etc.In an example, packet duplication may be used for user-plane and/orcontrol-plane traffic. In an example, LTE-NR dual connectivity may usepacket duplication. In an example, the packet data convergence protocol(PDCP) function in a transmitter may enable packet duplication and thePDCP function in the receiver may enable duplicate packet removal. In anexample, radio link control (RLC) retransmission (e.g., ARQ) may not beused for URLLC, e.g., for meeting the user-plane latency requirements.In an example, redundancy schemes operating below PDCP and/or in carrieraggregation (CA) scenarios may be used for the reliability/latencyenhancement of URLLC.

In an example in NR, multi-connectivity (MC) may comprisedual-connectivity (DC) and/or carrier aggregation (CA). In an example,multi-connectivity may comprise collocated eNBs/gNBs and/ornon-collocated eNBs/gNBs. In an example, packet duplication may be basedon PDCP with a DC architecture. In an example, packet duplication may beused with centralized and/or non-centralized PDCP. In an example, packetduplication backhaul may be used with different latencies and/ordifferent scheduler implementations (e.g., in LTE-NR integration).

In an example, PDCP duplication may be used in NR. In an example, packetduplication may be in lowers layers, e.g., MAC. In an example, DC mayuse a plurality of (e.g., two) MAC entities. In an example, the MACentities and/or the schedulers in MAC entities may be coordinated. In anexample, in CA, a common MAC entity, e.g., a scheduler, may controltransmissions on a plurality of carriers. In an example, packetduplication may be used with CA. In an example, the MAC layer may haveinformation (e.g., timely information) on radio channel qualitymeasurements (such as channel state information (CSI) report, ACK/NACKfeedback, etc.).

In an example, TTI repetitions may be configured e.g., incoverage-limited scenarios. TTI repetitions may increase thereliability. TTI repetitions may increase latency. In an example, theTTI repetitions may be performed on one or more carriers. In an example,with TTI repetitions, the received soft bits of multiple consecutivetransmissions within a same HARQ process may be combined. Soft combininggain and/or incremental redundancy gains (e.g., if supported within TTIrepetitions) may be achieved.

In an example, duplicate transmission of MAC PDUs (e.g., same transportblocks) may be used. In an example, two or more transport blocks (TBs)of a same size may be created by MAC multiplexing and assembly entity.In an example, two or more TBs may comprise a same duplicated MAC PDU.In an example, HARQ transmissions among carriers may be coupled, e.g.,using a same transport block size (TBS). In an example, a receiver mayuse joint decoding (e.g., soft combining) of the transmissions. In anexample, HARQ feedback may be aligned among the carriers. The RLCduplicate discard function may be used to handle the duplicates.

In an example, duplicate transmission of MAC SDUs, e.g., RLC PDUs and/orRLC PDU segments may be used. In an example, MAC multiplexing andassembly entity may transmit MAC SDU duplicates via a plurality ofcarriers. In an example, the HARQ transmissions among the carriers, e.g.transport block size (and required spectrum), HARQ feedbacktransmissions, etc. may be independent. In an example, a plurality ofcarrier bandwidths (e.g., numerologies) and/or carriers with differenttraffic loads may be considered. In an example, RLC duplicate discardfunction may be used at the receiver to handle the duplicates.

In an example, NR MAC may support data duplication in carrieraggregation. In an example, the MAC may be configured to duplicate andtransmit MAC SDUs among a plurality of carries. In an example, HARQoperation of the transmissions may be independent. In an example,duplicate discard functionality of RLC may be used to discard theduplicates.

In an example, PDCP split bearer and/or PDCP split bearer architecturemay be used in CA. In an example, a plurality of RLC entities may beconfigured corresponding to a PDCP bearer. In an example, PDCP maycomprise the duplication function and/or duplicate discard function. Inan example, duplicate data may be mapped to two or more logicalchannels. In an example, MAC multiplexing entity may map data of the RLCentities to different carriers that may be independently transmitted bythe HARQ entities associated with the corresponding carriers. In anexample, logical channel carrier restrictions may be applied. In anexample, one or more flags may be configured for a logical channel toallow/forbid scheduling on one or more carriers. In an example, PDCPsplit bearer with duplication function may be used in CA architecture.In an example, duplication for CA may build on the PDCP split bearer forduplication to two or more logical channels associated with a MACentity. In an example, for duplication with CA, transmissionrestrictions may be configured for one or more carriers per logicalchannel.

In an example, NR MAC may support data duplication in carrieraggregation by transmitting data from different logical channels usingdifferent cells/carriers (e.g. by defining carrier restrictions for alogical channel). Data duplication and duplicate discard may be done inPDCP layer. The PDCP split bearer may be configured with a plurality oflogical channels associated to a same cell group/MAC. In an example,data duplicated on PDCP and provided to the different logical channelsmay be transmitted by MAC via a plurality of carriers.

In an example, using MAC duplication, two or more same transport blocks(TB) may be transmitted across a plurality of legs, e.g., using one ormore MCS and/or redundancy versions. In an example, separate HARQfunctions may operate in each leg, e.g., in CA with a HARQ entitycomprising a plurality of HARQ processes for a carrier. In an example, aTB may be encoded/decoded and/or go through HARQ process independently.A duplication detection/removal mechanism may be used in MAC layer. Inan example, upper layers may handle the duplication detection.

In an example, packet duplication in MAC may be above the HARQ function(e.g., a function per leg) or at the HARQ function level (e.g., singlefunction for sending and combining redundancy versions). In an example,packet duplication in MAC above the HARQ function (e.g., one functionper leg) may use a duplication detection/removal function in MAC, or inhigher layers.

In an example, packet duplication may be used for user-plane and/orcontrol-plane in NR PDCP. In an example, redundancy schemes operatingbelow PDCP may be used. In an example, a duplication scheme operating atthe MAC sublayer may enable a plurality of transmissions of a transportblock over a plurality of resource sets to provide diversity gain e.g.,against fading, interference and/or link blockage (e.g., shadowing). Thedifferent resource sets may be separated in time, frequency and/or spacedomains. In an example, at the receiver, the transmissions may besoft-combined and/or processed separately.

In an example, PDCP packet duplication may be configured by radioresource configuration (RRC) signaling, e.g., per bearer and/or splitradio bearer. In an example, PDCP packet duplication may be configuredper UE using higher layer signaling (e.g., RRC). In an example, packetduplication may be enabled/disabled considering e.g., UE mobility, cellresource availability, backhaul loads and latency, etc. In an example,PDCP packet duplication may be activated or deactivated dynamicallythrough downlink control signaling (e.g., physical layer and/or MAClayer signaling). In an example, a UE may initiate duplication e.g.,based on triggering one or more criteria (e.g. measurements of L1, L2signals, or radio resource management (RRM) and/or radio link monitoring(RLM) events, etc.). In an example, a UE may autonomously activate ordeactivate PDCP packet duplication based on one or more configuredcriteria. The one or more criteria may be configured e.g., with RRC. Inan example, a UE may receive a configuration of a prohibit timer (e.g.,PDCP duplication prohibit timer). In an example, a UE may start thetimer when it receives control signaling from gNB/network indicatingthat PDCP duplication may be deactivated. The UE may autonomouslyactivate duplication when the timer is expired. The timer may be set toinfinity to disable UE autonomous activation of PDCP duplication.

In an example, with URLLC packet duplication at PDCP, a UE may reportdata in its PDCP buffer to a MAC entity in multi-connectivity. In anexample, duplicated data may be considered as new data available fortransmission. In an example, the duplicated data may be reported andtransmitted, e.g., in the same manner as other data. In an example, forMAC buffer status reporting, the UE MAC may include amount of dataresulting from the PDCP duplication function as data available fortransmission. In an example, data duplicates may use separate uplinkgrants. In an example, a grant may be unique per cell group. In anexample, assignment between a PDCP duplicate PDU and a MAC entity may bedone when the duplicate PDUs are generated in PDCP. In an example, a UEmay trigger BSR/SR to an applicable MAC entity. In an example, forresource allocation based on dynamic scheduling, a UE may assign aduplicate PDCP PDU to different MAC entities and triggers BSR/SR for anapplicable MAC entity when PDCP duplication is active.

In an example, PDCP at a transmitter may support duplicated packettransmission over a plurality of links. In an example, PDCP at areceiver may perform duplication detection/removal. In an example, for aCA scenario, where transmission points on different carrier frequenciesmay be connected by ideal backhaul, PDCP duplication may be applied,e.g., based on Dual-Connectivity/Multi-Connectivity framework. In anexample, PDCP duplication based on Dual-Connectivity/Multi-Connectivityframework may be applied to scenarios where transmission points ondifferent carrier frequencies are connected by ideal backhaul. In anexample redundancy operation below PDCP, duplication may be at RLClayer. In an example, RLC entity at a transmitter may make duplicatetransmissions of a PDU. In an example, RLC entity at a receiver side mayremove received duplications. In an example, redundancy operation at MAClayer may be MAC SDU duplication and/or autonomous HARQ redundanttransmission.

In an example, a RLC PDU may correspond to a PDCP PDU. In an example, aduplicated RLC PDU may comprise a duplicated PDCP PDU. In an example,duplicate transmission of RLC PDUs may be equivalent to duplicatetransmission of PDCP PDUs. In an example carrier aggregation (CA)scenario (e.g., ideal backhaul), PDCP entity and RLC entity may share asame topology of transmission points and backhaul structure. In anexample, MAC SDU duplication may use one HARQ entity per componentcarrier/cell. In an example, a MAC TB may be transmitted by a HARQprocess of a HARQ entity at a carrier. The duplicated MAC SDUs may be inthe respective TBs generated for different carriers. The duplication maybe at MAC SDU level, which may correspond to a RLC PDU and in turn to aPDCP PDU. In an example, a MAC SDU may not have a sequence number in NR.

In an example, different redundancy versions of a MAC TB may betransmitted over a plurality of aggregated carriers. In an example, aHARQ process may transmit different RVs of a MAC TB over a plurality ofcomponent carriers. At the receiver, soft combining may be used. In anexample, a MAC TB may consist of a plurality of MAC SDUs/RLC PDUs/PDCPPDUs. In an example, packet duplication may be applied to data radiobearers (DRBs)/logical channels carrying URLLC like services.

In an example, a gNB may configure/enable/disable data redundancy belowPDCP layer, considering radio conditions and functionalities provisionedin other layers. In an example, a logical channel may be mapped to oneor more numerologies/TTI durations/transmission durations. In anexample, if a logical channel may be mapped to one or morenumerologies/TTI durations/transmission durations, duplicate data of thelogical channel may be transmitted over the one or more numerologies(e.g., in a single carrier and/or multiple carriers).

In an example, support for packet duplication function may be configuredper radio bearer. In an example, a UE may enable/disable packetduplication function. In an example, the gNB may indicate the UE to turnon/off the duplication function (e.g., using RRC and/or physical layerand/or MAC layer signaling). In an example, for a radio bearer withpacket duplicate function, enabling/disabling packet duplicationfunction may be dynamically controlled.

In an example, for UL packet duplication using Dual connectivity inNR-NR inter-working scenario, the UL PDCP entity of the radio bearer maycoordinate the transmission of the UL PDCP PDU towards the secondarycell group (SCG) and master cell group (MCG) by indicating the dataavailability of the same UL PDCP SDU in the buffer status reports (BSRs)to both MCG and SCG. In an example, the wireless device may transmitPDUs of a same PDCP SDU in the logical channels of the MCG and SCG. Inan example, the UL PDCP entity may maintain the data availability forthe MCG and the SCG separately (e.g. by maintaining separate PDCP SDUbuffers for MCG and SCG, or by maintaining separate available orunavailable indications corresponding to SDUs in the same buffer). In anexample, whether to allow for duplication and the number of duplicationsmay be configurable via RRC signaling per radio bearer.

In an example, the BSR procedure and SR triggering may be similar as innormal operation without packet duplication. The BSR and SR may beseparately triggered by the MAC entities for MCG and SCG on the UE side.In an example, the logical channel(s) corresponding to URLLC may beconfigured to have highest priority and/or higher priority than othertraffic channels. In an example, the logical channel prioritization(LCP) may prioritize the URLLC logical channel(s) when generating andsending the MAC PDU to the lower layers for the UL grant (e.g.,configured or dynamic) corresponding to the numerology configured forthe URLLC logical channel. In an example, for the DL packet duplicationat the PDCP level, the DL RX PDCP entity may discard the duplicated PDCPPDUs e.g., if duplicate reception is detected.

In an example, RRM measurement for mobility in the connected mode mayprovide information for the gNB/network to manage addition and removalof a cell in multi-connectivity configuration. In an example,semi-static (e.g., using RRC) and dynamic signaling may control whichlegs of a split bearer, data may be duplicated. In an example, RRMmeasurements may be considered as baseline input for the dataduplication control, e.g., a set of RSRP threshold.

In an example, for DL and UL, duplication for CA may use PDCPduplication to more than one logical channel. In an example, theduplicated PDCP PDUs may be sent over a plurality of (e.g., different)carriers. In an example, the logical channels with data and the logicalchannels with duplicate data may be handled by one MAC entity. In anexample, the logical channels with data and the logical channels withduplicate data may be handled by two or more MAC entities.

In an example, a wireless device may receive one or more messagescomprising one or more radio resource configuration (RRC) messages fromone or more base stations (e.g., one or more NR gNBs and/or one or moreLTE eNBs and/or one or more eLTE eNBs, etc.). In an example, the one ormore messages may comprise configuration parameters for a plurality oflogical channels. In an example, the one or messages may comprise alogical channel identifier for each of the plurality of logicalchannels. In an example, the logical channel identifier may be one of aplurality of logical channel identifiers. In an example, the pluralityof logical channel identifiers may be pre-configured. In an example, thelogical channel identifier may be one of a plurality of consecutiveintegers.

In an example, the plurality of logical channels configured for awireless device may correspond to one or more bearers. In an example,there may be one-to-one mapping/correspondence between a bearer and alogical channel. In an example, there may be one-to-manymapping/correspondence between one or more bearers and one or morelogical channels. In an example, a bearer may be mapped to a pluralityof logical channels. In an example, data from a packet data convergenceprotocol (PDCP) entity corresponding to a bearer may be duplicated andmapped to a plurality of radio link control (RLC) entities and/orlogical channels. In an example, scheduling of the plurality of logicalchannels may be performed by a single medium access control (MAC)entity. In an example, scheduling of the plurality of logical channelsmay be performed by a two or more MAC entities. In an example, a logicalchannel may be scheduled by one of a plurality of MAC entities. In anexample, the one or more bearers may comprise one or more data radiobearers. In an example, the one or more bearers may comprise one or moresignaling radio bearers. In an example, the one or more bearers maycorrespond to one or more application and/or quality of service (QoS)requirements. In an example, one or more bearers may correspond toultra-reliable low latency communications (URLLC) applications and/orenhanced mobile broadband (eMBB) applications and/or massive machine tomachine communications (mMTC) applications.

In an example, a first logical channel of the plurality of logicalchannels may be mapped to one or more of a plurality of transmissiontime intervals (TTIs)/transmission durations/numerologies. In anexample, a logical channel may not be mapped to one or more of theplurality of TTIs/transmission durations/numerologies. In an example, alogical channel corresponding to a URLLC bearer may be mapped to one ormore first TTIs/transmission durations and a logical corresponding to aneMBB application may be mapped to one or more second TTIs/transmissiondurations, wherein the one or more first TTIs/transmission duraions mayhave shorter duration than the one or more second TTIs/transmissiondurations. In an example, the plurality of TTIs/transmissiondurations/numerologies may be pre-configured at the wireless device. Inan example, the one or more messages may comprise the configurationparameters of the plurality of TTIs/transmission durations/numerologies.In an example, a base station may transmit a grant/DCI to a wirelessdevice, wherein the grant/DCI may comprise indication of a cell and/or aTTI/transmission durations/numerology that the wireless device maytransmit data. In an example, a first field in the grant/DCI mayindicate the cell and a second field in the grant/DCI may indicate theTTI/transmission durations/numerology. In an example, a field in thegrant/DCI may indicate both the cell and the TTI/transmissionduration/numerology.

In an example, the one or more messages may comprise a logical channelgroup identifier for one or more of the plurality of the logicalchannels. In an example, one or more of the plurality of logicalchannels may be assigned a logical channel group identifier n, 0≤n≤N(e.g., N=3, or 5, or 7, or 11 or 15, etc.). In an example, the one ormore of the plurality of logical channels with the logical channel groupidentifier may be mapped to a same one or more TTIs/transmissiondurations/numerologies. In an example, the one or more of the pluralityof logical channels with the logical channel group identifier may onlybe mapped to same one or more TTIs/transmission durations/numerologies.In an example, the one more of the plurality of logical channels maycorrespond to a same application and/or QoS requirements. In an example,one or more first logical channels may be assigned logical channelidentifier(s) and logical channel group identifier(s) and one or moresecond logical channels may be assigned logical channel identifier(s).In an example, a logical channel group may comprise of one logicalchannel.

In an example, the one or more messages may comprise one or more firstfields indicating mapping between the plurality of logical channels andthe plurality of TTIs/transmission durations/numerologies and/or cells.In an example, the one or more first fields may comprise a first valueindicating a logical channel is mapped to one or more firstTTI/transmission duration shorter than or equal to the first value. Inan example, the one or more first fields may comprise a second valueindicating a logical channel is mapped to one or more secondTTI/transmission durations longer than or equal to the second value. Inan example, the one or more first fields may comprise and/or indicateone or more TTIs/transmission durations/numerologies and/or cells that alogical channel is mapped to. In an example, the mapping may beindicated using one or more bitmaps. In an example, if a value of 1 in abitmap associated with a logical channel may indicate that the logicalchannel is mapped to a corresponding TTI/transmissionduration/numerology and/or cell. In an example, if a value of 0 in thebitmap associated with a logical channel may indicate that the logicalchannel is not mapped to a corresponding TTI/transmissionduration/numerology and/or cell. In an example, the one or more messagesmay comprise configuration parameters for the plurality of the logicalchannels. In an example, the configuration parameters for a logicalchannel may comprise an associated bitmap for the logical channelwherein the bitmap may indicate the mapping between the logical channeland the plurality of TTIs/transmission durations/numerologies and/orcells.

In an example, a first logical channel may be assigned at least onefirst logical channel priority. In an example, the first logical channelmay be assigned one or more logical channel priorities for one or moreTTIs/transmission durations/numerologies. In an example, the firstlogical channel may be assigned a logical channel priority for each ofthe plurality of TTIs/transmission durations/numerologies. In anexample, a logical channel may be assigned a logical channel priorityfor each of one or more of the plurality of TTIs/transmissiondurations/numerologies. In an example, a logical channel may be assigneda logical channel priority for each of one or more TTIs/transmissiondurations/numerologies wherein the logical channel is mapped to the eachof the one or more TTIs/transmission durations/numerologies. In anexample, the one or more messages may comprise one or more second fieldsindicating priorities of a logical channel on one or moreTTIs/transmission durations/numerologies. In an example, the one or moresecond fields may comprise one or more sequences indicating prioritiesof a logical channel on one or more TTIs/transmissiondurations/numerologies. In an example, the one or more second fields maycomprise a plurality of sequences for the plurality of logical channels.A sequence corresponding to a logical channel may indicate thepriorities of the logical channel on the plurality of TTIs/transmissiondurations/numerologies/cells or one or more of the plurality ofTTIs/transmission durations/numerologies/cells. In an example, thepriorities may indicate mapping between a logical channel and one ormore TTIs/transmission durations/numerologies. In an example, a priorityof a logical channel with a given value (e.g., zero or minus infinity ora negative value) for a TTI/transmission duration/numerology mayindicate that the logical channel is not mapped to the TTI/transmissionduration/numerology. FIG. 15 illustrates an example with threeTTIs/transmission durations/numerologies and three logical channels(LC₁, LC₂, LC₃) wherein LC₁ is mapped to TTI₁/transmission duration₁,TTI₂/transmission duration₂, and TTI₃/transmission duration₃ and LC₂ ismapped to TTI₂/transmission duration₂ and TTI₃/transmission duration₃and LC₃ is mapped to TTI₃/transmission duration₃. In an example,priorities of LC₁ on TTI₁/transmission duration₁, TTI₂/transmissionduration₂, and TTI₃/transmission duration₃ may be indicated as (1, 2,3), priorities of LC₂ on TTI₁/transmission duration₁, TTI₂/transmissionduration₂, and TTI₃/transmission duration₃ may be indicated as (0, 1,2), priorities of LC₃ on TTI₁/transmission duration₁, TTI₂/transmissionduration₂, and TTI₃/transmission duration₃ may be indicated as (0, 0,1). In an example, sizes of the sequence may be variable. In an example,a size of a sequence associated with a logical channel may be a numberof TTIs/transmission durations/numerologies to which the logical channelis mapped. In an example, the sizes of the sequence may be fixed, e.g.,the number of TTIs/transmission durations/numerologies/cells.

In an example, a TTI/transmission duration/numerology for a grant (e.g.,as indicated by the grant/DCI) may not accept data from one or morelogical channels. In an example, the one or more logical channels maynot be mapped to the TTI/transmission duration/numerology indicated inthe grant. In an example, a logical channel of the one or more logicalchannels may be configured to be mapped to one or more TTIs/transmissiondurations/numerologies and the TTI/numerology for the grant may not beamong the one or more TTIs/transmission durations/numerologies. In anexample, a logical channel of the one or more logical channels may beconfigured with a max-TTI/transmission duration parameter indicatingthat the logical channel may not be mapped to a TTI/transmissionduration longer than max-TTI/transmission duration, and the grant may befor a TTI/transmission duration longer than max-TTI/transmissionduration. In an example, a logical channel may be configured with amin-TTI/transmission duration parameter indicating that the logicalchannel may not be mapped to a TTI/transmission duration shorter thanmin-TTI/transmission duration, and the grant may be for aTTI/transmission duration shorter than min-TTI/transmission duration. Inan example, a logical channel may not be allowed to be transmitted on acell and/or one or more numerologies/transmission durations and/or oneor more numerologies of a cell. In an example, a logical channel maycontain duplicate data and the logical channel may be restricted so thatthe logical channel is not mapped to a cell/transmissionduration/numerology. In an example, the logical channel may not beconfigured with an upper layer configuration parameter 1aa-allowed andthe cell may be an LAA cell.

In an example, a MAC entity and/or a multiplexing and assembly entity ofa MAC entity may perform a logical channel prioritization (LCP)procedure to allocate resources of one or more grants, indicated to awireless device by a base station using one or more DCIs, to one or morelogical channel. In an example, the timing between a grant/DCI receptiontime at the wireless device and transmission time may be dynamicallyindicated to the wireless device (e.g., at least using a parameter inthe grant/DCI). In an example, timing between a grant/DCI reception timeat the wireless device and transmission time may be fixed/preconfiguredand/or semi-statically configured. In an example, the LCP procedure forNR may consider the mapping of a logical channel to one or morenumerologies/transmission durations/TTIs, priorities of a logicalchannel on the one or more numerologies/transmission durations/TTIs, thenumerology/transmission duration/TTI indicated in a grant, etc. The LCPprocedure may multiplex data from one or more logical channels to form aMAC PDU. The amount of data from a logical channel included in a MAC PDUmay depend on the QoS parameters of a bearer and/or service associatedwith the logical channel, priority of the logical channel on thenumerology/TTI/transmission duration indicated in the grant, etc. In anexample, one or more grants may be processed jointly at a wirelessdevice (e.g., resources of the one or more grants are allocatedsubstantially at a same time). In an example, one or more first grantsof the one or more grants may be grouped into a grouped grant withcapacity equal to sum of the capacities of the one or more first grantsand the resources of the grouped grant may be allocated to one or morelogical channels.

An example, PDCP packet duplication procedure is shown in FIG. 16. In anexample, duplication may be configured for a bearer by RRC. In anexample, in response to configuration of PDCP duplication for a radiobearer, an additional RLC entity and an additional logical channel maybe added to the radio bearer to handle the duplicated PDCP protocol dataunits (PDUs). In an example, duplication at PDCP may comprise sendingthe same PDCP PDUs twice: once on the original RLC entity and a secondtime on the additional RLC entity. With two independent transmissionpaths, packet duplication may increase reliability and may reducelatency and is especially beneficial for URLLC services. In an example,when duplication occurs, the original PDCP packet and the correspondingduplicate may not be transmitted on the same carrier. The two differentlogical channels may either belong to the same MAC entity (e.g., incarrier aggregation) or to different MAC entities (dual connectivity).In the carrier aggregation case as shown in FIG. 16, logical channelmapping restrictions may be used in MAC to ensure that the logicalchannel carrying the original PDCP PDUs and logical channel carrying thecorresponding duplicates may not be sent on the same carrier. As shownin FIG. 16, a first logical channel of the bearer may be mapped to oneor more first carriers and a second logical channel of the bearer may bemapped to one or more second carriers. In an example, the one or morefirst carriers may be different from the one or more second carriers.

Example embodiments enhance triggering conditions for a wireless deviceto enable/disable packet duplication function.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signaling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signaling (e.g., PDCCH like signaling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria. In anexample, the one or more criteria may comprise frequent undelivered datapackets measured at the PDCP layer (e.g., frequent undelivered PDCPPDUs). In an example, a threshold may be configured to triggerenabling/disabling the PDCP function for a bearer. In an example, thethreshold may be pre-configured. In an example, the threshold may beconfigured by higher layers (e.g., RRC). In an example, the thresholdmay be same for the bearers configured with packet duplication. In anexample, the threshold may be configured per bearer configured withpacket duplication. In an example, the threshold may be cell-specific.In an example, the threshold may indicate a percentage of PDCP PDUs thatwere not successfully transmitted/delivered. In an example, thepercentage may be measured for a time window. In an example, the timewindow may be pre-configured. In example, the value of time window maybe indicated by higher layers (e.g., RRC). In an example, the MAC entitymay duplicate the PDCP PDUs for a bearer for which the duplication isconfigured/enabled and may not duplicate PDCP PDUs for a bearer forwhich the duplication is disabled (not configured). In an example, aPDCP PDU and a duplicate PDCP PDU may correspond to different RLCentities/logical channels. In an example, the wireless device mayreceive one or more DCIs/grants for transmission on one or more cellse.g., for one or more numerologies/TTIs on the one or more cells. ADCI/grant may indicate the transmission parameters such as resources fortransmission, power control commands, HARQ parameters, modulation andcoding scheme (MCS), etc. The wireless device may perform a logicalchannel prioritization/multiplexing procedure and may allocate theresources of the grant/DC to one or more logical channels to create aMAC PDU. In an example, the one or more logical channels may compriselogical channels with data and/or duplicate data. In an example, the MAClayer may deliver the MAC PDU to Physical layer to create a transportblock (TB). The wireless device may calculate transmission power for theTB using at least the power control commands in the grant/DCI. ThePhysical layer may map the TB to the time/frequency resources indicatedin the DCI/grant and may transmit the TB.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signaling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signaling (e.g., PDCCH like signaling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria. In anexample, the one or more criteria may comprise frequent undelivered datapackets measured at the RLC layer (e.g., frequent undelivered RLC PDUscorresponding to the bearer/PDCP entity configured with packetduplication). In an example, a threshold may be configured to triggerenabling/disabling the PDCP function for a bearer. In an example, thethreshold may be pre-configured. In an example, the threshold may beconfigured by higher layers (e.g., RRC). In an example, the thresholdmay be same for the bearers configured with packet duplication. In anexample, the threshold may be configured per bearer configured withpacket duplication. In an example, the threshold may be cell-specific.In an example, the threshold may indicate a percentage of RLC PDUs,corresponding to a bearer configured with duplication, that were notsuccessfully transmitted/delivered. In an example, the percentage may bemeasured for a time window. In an example, the time window may bepre-configured. In example, the value of time window may be indicated byhigher layers (e.g., RRC). In an example, the MAC entity may duplicatethe PDCP PDUs for a bearer for which the duplication isconfigured/enabled and may not duplicate PDCP PDUs for a bearer forwhich the duplication is disabled (not configured). In an example, aPDCP PDU and duplicate PDCP PDU may correspond to different RLCentities/logical channels. In an example, the wireless device mayreceive one or more DCIs/grants for transmission on one or more cellse.g., for one or more numerologies/TTIs/transmission durations on theone or more cells. A DCI/grant may indicate the transmission parameterssuch as resources for transmission, power control commands, HARQparameters, modulation and coding scheme (MCS), etc. The wireless devicemay perform a logical channel prioritization/multiplexing procedure andmay allocate the resources of the grant/DC to one or more logicalchannels to create a MAC PDU. In an example, the one or more logicalchannels may comprise logical channels with data and/or duplicate data.In an example, the MAC layer may deliver the MAC PDU to Physical layerto create a transport block (TB). The wireless device may calculatetransmission power for the TB using at least the power control commandsin the grant/DCI. The Physical layer may map the TB to thetime/frequency resourced indicates in the DCI/grant and may transmit theTB.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signaling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signaling (e.g., PDCCH like signaling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria. In anexample, the one or more criteria may comprise frequent undelivered datapackets measured at the PHY/MAC layer (e.g., frequent HARQ NACKs and/orpoor channels conditions on one or more cells/numerologies mapped to alogical channel corresponding to a bearer configured with packetduplication). In an example, a threshold may be configured to triggerenabling/disabling the PDCP function for a bearer. In an example, thethreshold may be pre-configured. In an example, the threshold may beconfigured by higher layers (e.g., RRC). In an example, the thresholdmay be same for the bearers configured with packet duplication. In anexample, the threshold may be configured per bearer configured withpacket duplication. In an example, the threshold may be cell-specific.In an example, the threshold may indicate a percentage/number of HARQNACKs received for packets transmitted on one or more cells/numerologieswhere a logical channel corresponding to a bearer configured withduplication, is mapped to. In an example, the percentage may be measuredfor a time window. In an example, the time window may be pre-configured.In example, the value of time window may be indicated by higher layers(e.g., RRC). In an example, the threshold may indicate a thresholdchannel quality indicator (CQI). In an example, the MAC entity mayduplicate the PDCP PDUs for a bearer for which the duplication isconfigured/enabled and may not duplicate PDCP PDUs for a bearer forwhich the duplication is disabled (not configured). In an example, aPDCP PDU and duplicate PDCP PDU may correspond to different RLCentities/logical channels. In an example, the wireless device mayreceive one or more DCIs/grants for transmission on one or more cellse.g., for one or more numerologies/TTIs/transmission durations on theone or more cells. A DCI/grant may indicate the transmission parameterssuch as resources for transmission, power control commands, HARQparameters, modulation and coding scheme (MCS), etc. The wireless devicemay perform a logical channel prioritization/multiplexing procedure andmay allocate the resources of the grant/DC to one or more logicalchannels to create a MAC PDU. In an example, the one or more logicalchannels may comprise logical channels with data and/or duplicate data.In an example, the MAC layer may deliver the MAC PDU to Physical layerto create a transport block (TB). The wireless device may calculatetransmission power for the TB using at least the power control commandsin the grant/DCI. The Physical layer may map the TB to thetime/frequency resources indicated in the DCI/grant and may transmit theTB.

Example embodiment enhance efficiency of logical channel multiplexing bydiscarding data that has already been transmitted from logical channelscorresponding to a bearer that is configured with packet duplication.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signaling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signaling (e.g., PDCCH like signaling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria (e.g., asdescribed in embodiments in this disclosure). In an example, the MACentity may duplicate the PDCP PDUs for a bearer for which theduplication is configured/enabled and may not duplicate PDCP PDUs for abearer for which the duplication is disabled (not configured). In anexample, a PDCP PDU and duplicate PDCP PDUs may correspond to differentRLC entities/logical channels. In an example, if a first logical channelwith PDCP PDUs (or duplicate PDCP PDUs) of a bearer configured withpacket duplication contains a first amount of data (e.g., X bytes or XPDCP PDUs/RLC SDUs) and a second logical channel with duplicate PDCPPDUs (or PDCP PDUs) of a bearer configured with packet duplicationcontains a second amount of data (e.g., Y bytes or Y PDCP PDUs/RLCSDUs), and the first amount of data is larger than the second amount ofdata, the wireless device MAC entity may discard a portion of data inthe first logical channel that has been transmitted and acknowledged(e.g., HARQ ACKed and/or RLC ACKed). In an example, if the first amountof data is X bytes and the second amount of data is Y bytes and X islarger than Y, the wireless device may discard as much as (X-Y-unACKeddata) on top of the buffer for the first logical channel. In an examplewith more than one logical channel containing duplicate PDCP PDUs, thewireless device MAC entity may discard a portion of data that has beentransmitted and acknowledged (e.g., HARQ ACKed and/or RLC ACKed) in atleast one logical channel from a plurality of logical channelscorresponding to the same bearer. In an example, if the buffer for alogical channel that contains PDCP PDUs or duplicate PDCP PDUs for abearer configured with packet duplication is emptied and the last datain the buffer is acknowledged (e.g., HARQ ACKed and/or RLC ACKed) aftertransmission, the wireless device MAC entity may empty one or morelogical channels corresponding to the radio bearer (e.g., logicalchannels containing PDCP PDUs or duplicate PDCP PDUs from the bearer).In an example, the wireless device may perform the data discardingprocess described in configured times. In an example, the configuredtimes for the discarding process may be pre-configured. In an example,the configured times may be indicated to the wireless device (e.g.,using RRC and/or physical layer/MAC layer signaling). In an example, thewireless device may perform duplicate data discard when a buffer statusreport is triggered and/or when the wireless device creates the bufferstatus report MAC CE. In an example, the wireless device may receive oneor more DCIs/grants for transmission on one or more cells e.g., for oneor more numerologies/TTIs/transmission durations on the one or morecells. A DCI/grant may indicate the transmission parameters such asresources for transmission, power control commands, HARQ parameters,modulation and coding scheme (MCS), etc. The wireless device may performa logical channel prioritization/multiplexing procedure and may allocatethe resources of the grant/DC to one or more logical channels to createa MAC PDU. In an example, the one or more logical channels may compriselogical channels with data and/or duplicate data. In an example, the MAClayer may deliver the MAC PDU to Physical layer to create a transportblock (TB). The wireless device may calculate transmission power for theTB using at least the power control commands in the grant/DCI. ThePhysical layer may map the TB to the time/frequency resources indicatedin the DCI/grant and may transmit the TB.

Example embodiments enhance buffer status reporting when one or morebearers are configured with packet duplication.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signaling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signaling (e.g., PDCCH like signaling, MAC CE, etc.).In an example, the MAC entity may duplicate the PDCP PDUs for a bearerfor which the duplication is configured/enabled and may not duplicatePDCP PDUs for a bearer for which the duplication is disabled (notconfigured). In an example, a PDCP PDU and duplicate PDCP PDUs maycorrespond to different RLC entities/logical channels. In an example, awireless device MAC entity may perform data discard process (e.g., asdescribed in embodiments in this disclosure). In an example, a wirelessdevice MAC entity may perform data discard process (e.g., as describedin embodiments in this disclosure) when a buffer status report istriggered and/or when a buffer status report MAC CE is created. One ormore logical channels corresponding to a bearer configured with packetduplication for which packet duplication is enabled (e.g., enabled bythe base station) may have substantially same amount of data (e.g., whenthe buffer status report MAC CE is created). In an example, a logicalchannel of the one or more logical channels may have as much asunacknowledged data less data in the logical channel's buffer comparedto other logical channels in the one or more logical channels. In anexample, if the base station configures/enables the packet duplicationfor a bearer configured for the wireless device, a plurality of logicalchannels may correspond to bearer. In an example, the buffer statusreport may comprise buffer status of one logical channels correspondingto the bearer (e.g., logical channels comprising PDCP PDUs). In anexample, the wireless device may receive one or more DCIs/grants fortransmission on one or more cells e.g., for one or morenumerologies/TTIs/transmission durations on the one or more cell. ADCI/grant may indicate the transmission parameters such as resources fortransmission, power control commands, HARQ parameters, modulation andcoding scheme (MCS), etc. The wireless device may perform a logicalchannel prioritization/multiplexing procedure and may allocate theresources of the grant/DC to one or more logical channels to create aMAC PDU. In an example, the one or more logical channels may compriselogical channels with data and/or duplicate data. In an example, the MAClayer may deliver the MAC PDU to Physical layer to create a transportblock (TB). The wireless device may calculate transmission power for theTB using at least the power control commands in the grant/DCI. ThePhysical layer may map the TB to the time/frequency resources indicatedin the DCI/grant and may transmit the TB.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signaling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, a UEmay autonomously enable/disable the PDCP packet duplication for a bearerconsidering one or more criteria (e.g., as described in embodiments inthis disclosure). In an example, the MAC entity may duplicate the PDCPPDUs for a bearer for which the duplication is configured/enabled andmay not duplicate PDCP PDUs for a bearer for which the duplication isdisabled and/or not configured. In an example, a PDCP PDU and duplicatePDCP PDUs may correspond to different RLC entities/logical channels. Inan example, a wireless device MAC entity may perform data discardprocess (e.g., as described in embodiments in this disclosure). In anexample, a wireless device MAC entity may perform data discard process(e.g., as described in embodiments in this disclosure) when a bufferstatus report is triggered and/or when a buffer status report MAC CE iscreated. One or more logical channels corresponding to a bearerconfigured with packet duplication for which packet duplication isenabled (e.g., enabled autonomously by the wireless device) may havesubstantially same amount of data (e.g., when the buffer status reportMAC CE is created). In an example, a logical channel of the one or morelogical channels may have as much as unacknowledged data less data inthe logical channel's buffer compared to other logical channels in theone or more logical channels. In an example, if the wireless deviceautonomously enables the packet duplication for a bearer configured forthe wireless device (and/or configured with packet duplication), aplurality of logical channels may correspond to bearer. In an example,the buffer status report may comprise buffer status of one logicalchannels corresponding to the bearer (e.g., logical channels comprisingPDCP PDUs). In an example, the buffer status report may comprise anindication that a logical channel has a corresponding logical channelwith duplicate data. In an example, the indication may be in form of abitmap. In an example, the indication may be in the MAC subheadercorresponding to the BSR. In an example, a value of one in the bit mapcorresponding to a logical channel may indicate that there is one ormore logical channels corresponding to the logical channel withduplicate data. In an example, the wireless device may receive one ormore DCIs/grants for transmission on one or more cells e.g., for one ormore numerologies/TTIs/transmission durations on the one or more cell. ADCI/grant may indicate the transmission parameters such as resources fortransmission, power control commands, HARQ parameters, modulation andcoding scheme (MCS), etc. The wireless device may perform a logicalchannel prioritization/multiplexing procedure and may allocate theresources of the grant/DC to one or more logical channels to create aMAC PDU. In an example, the one or more logical channels may compriselogical channels with data and/or duplicate data. In an example, the MAClayer may deliver the MAC PDU to Physical layer to create a transportblock (TB). The wireless device may calculate transmission power for theTB using at least the power control commands in the grant/DCI. ThePhysical layer may map the TB to the time/frequency resources indicatedin the DCI/grant and may transmit the TB.

Example embodiment enhance the HARQ retransmission procedure when one ormore bearers are configured with packet duplication.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signaling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signaling (e.g., PDCCH like signaling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria (e.g., asdescribed in embodiments in this disclosure). In an example, the MACentity may duplicate the PDCP PDUs for a bearer for which theduplication is configured/enabled and may not duplicate PDCP PDUs for abearer for which the duplication is disabled and/or not configured. Inan example, a PDCP PDU and duplicate PDCP PDUs may correspond todifferent RLC entities/logical channels. In an example, the base stationmay configure a logical channel (e.g., containing duplicate data) not tobe transmitted on one or more cells. In an example, the base station mayconfigure a logical channel not be transmitted on an LAA cell. In anexample, the base station may configure a logical channel with a bitmapindicating the one or more cells that a logical channel may and/or maynot be mapped to (e.g., data from the logical channel may and/or may notbe transmitted on). In an example, the wireless device may receive aDCI/grant for transmission on a first cell e.g., for a firstnumerology/TTI. The DCI/grant may indicate the transmission parameterssuch as resources for transmission, power control commands, HARQparameters, modulation and coding scheme (MCS), etc. In an example, thewireless device may multiplex data from a logical channel that isconfigured to not be transmitted on one or more cells and create a firstMAC PDU. In an example, the one or more cells may not comprise the firstcell. The physical layer may create a first TB using the first MAC PDU.The wireless device may calculate power for the first TB using at leastthe power control commands in the DCI/grant and may map the TB to theresources indicated in the DCI/grant and may transmit the TB. In anexample, a HARQ entity may handle transmission and/or retransmission oftransport blocks on a plurality of cells comprising the first cell. Inan example, the wireless device may receive a NACK and/or a secondDCI/grant indicating retransmission of the first TB (or a new redundancyversion of the first TB). In an example, the DCI/grant may indicate theHARQ retransmission of the first TB on a second cell of the plurality ofcells. In an example, the second cell may not be among the one or morecells. The wireless device may transmit the HARQ retransmission of thefirst TB e.g., using the transmission parameters (e.g., resources)indicated in the second DCI/grant. In an example, the HARQ entity may beindicated that there is a restriction for a TB (e.g., corresponding to aHARQ process) not to be transmitted on the one or more cells.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signaling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signaling (e.g., PDCCH like signaling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria (e.g., asdescribed in Example A embodiments). In an example, the MAC entity mayduplicate the PDCP PDUs for a bearer for which the duplication isconfigured/enabled and may not duplicate PDCP PDUs for a bearer forwhich the duplication is disabled and/or not configured. In an example,a PDCP PDU and duplicate PDCP PDUs may correspond to different RLCentities/logical channels. In an example, the base station may configurea logical channel (e.g., containing duplicate data) not to betransmitted on one or more cells. In an example, the base station mayconfigure a logical channel not be transmitted on an LAA cell. In anexample, the base station may configure a logical channel with a bitmapindicating the one or more cells that a logical channel may and/or maynot be mapped to (e.g., data from the logical channel may and/or may notbe transmitted on). In an example, the wireless device may receive aDCI/grant for transmission on a first cell e.g., for a firstnumerology/TTI/transmission duration. The DCI/grant may indicate thetransmission parameters such as resources for transmission, powercontrol commands, HARQ parameters, modulation and coding scheme (MCS),etc. In an example, the wireless device may multiplex data from alogical channel that is configured to not be transmitted on one or morecells and create a first MAC PDU. In an example, the one or more cellsmay not comprise the first cell. The physical layer may create a firstTB using the first MAC PDU. The wireless device may calculate power forthe first TB using at least the power control commands in the DCI/grantand may map the TB to the resources indicated in the DCI/grant and maytransmit the TB. In an example, a HARQ entity may handle transmissionand/or retransmission of transport blocks on a plurality of cellscomprising the first cell. In an example, the wireless device mayreceive a NACK and/or a second DCI/grant indicating retransmission ofthe first TB (or a new redundancy version of the first TB). In anexample, the DCI/grant may indicate the HARQ retransmission of the firstTB on a second cell of the plurality of cells. In an example, the secondcell may be among the one or more cells. The wireless device maytransmit the HARQ retransmission of the first TB e.g., using thetransmission parameters (e.g., resources) indicated in the secondDCI/grant.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signaling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signaling (e.g., PDCCH like signaling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria (e.g., asdescribed in Example A embodiments). In an example, the MAC entity mayduplicate the PDCP PDUs for a bearer for which the duplication isconfigured/enabled and may not duplicate PDCP PDUs for a bearer forwhich the duplication is disabled and/or not configured. In an example,a PDCP PDU and duplicate PDCP PDUs may correspond to different RLCentities/logical channels. In an example, the base station may configurea logical channel (e.g., containing duplicate data) not to betransmitted on one or more numerologies/TTIs/transmission durations. Inan example, the base station may configure a logical channel with abitmap indicating the one or more numerologies/TTIs/transmissiondurations that a logical channel may and/or may not be mapped to (e.g.,data from the logical channel may and/or may not be transmitted on). Inan example, the wireless device may receive a DCI/grant for transmissionon a first cell e.g., for a first numerology/TTI/transmission duration.The DCI/grant may indicate the transmission parameters such as resourcesfor transmission, power control commands, HARQ parameters, modulationand coding scheme (MCS), etc. In an example, the wireless device maymultiplex data from a logical channel that is configured to not betransmitted on one or more numerologies/TTIs/transmission durations andcreate a first MAC PDU. In an example, the one or morenumerologies/TTIs/transmission durations may not comprise the firstnumerology/TTI/transmission durations. The physical layer may create afirst TB using the first MAC PDU. The wireless device may calculatepower for the first TB using at least the power control commands in theDCI/grant and may map the TB to the resources indicated in the DCI/grantand may transmit the TB. In an example, HARQ entity may handletransmission and/or retransmission of transport blocks on a plurality ofTTIs/transmission durations/numerologies of the first cell comprisingthe first TTI/transmission duration/numerology. In an example, thewireless device may receive a NACK and/or a second DCI/grant indicatingretransmission of the first TB (or a new redundancy version of the firstTB). In an example, the DCI/grant may indicate the HARQ retransmissionof the first TB on a second TTI/transmission duration/numerology of theplurality of TTIs/transmission durations/numerologies. In an example,the second TTI/transmission duration/numerology may not be among the oneor more TTIs/transmission durations/numerologies. The wireless devicemay transmit the HARQ retransmission of the first TB e.g., using thetransmission parameters (e.g., resources) indicated in the secondDCI/grant. In an example, the HARQ entity may be indicated that there isa restriction for a TB (e.g., corresponding to a HARQ process) not to betransmitted on the one or more TTIs/numerologies.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signaling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signaling (e.g., PDCCH like signaling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria (e.g., asdescribed in embodiments in this disclosure). In an example, the MACentity may duplicate the PDCP PDUs for a bearer for which theduplication is configured/enabled and may not duplicate PDCP PDUs for abearer for which the duplication is disabled and/or not configured. Inan example, a PDCP PDU and duplicate PDCP PDUs may correspond todifferent RLC entities/logical channels. In an example, the base stationmay configure a logical channel (e.g., containing duplicate data) not tobe transmitted on one or more numerologies/TTIs/transmission durations.In an example, the base station may configure a logical channel with abitmap indicating the one or more numerologies/TTIs/transmissiondurations that a logical channel may and/or may not be mapped to (e.g.,data from the logical channel may and/or may not be transmitted on). Inan example, the wireless device may receive a DCI/grant for transmissionon a first cell e.g., for a first numerology/TTI/transmission duration.The DCI/grant may indicate the transmission parameters such as resourcesfor transmission, power control commands, HARQ parameters, modulationand coding scheme (MCS), etc. In an example, the wireless device maymultiplex data from a logical channel that is configured to not betransmitted on one or more numerologies/TTIs/transmission durations andcreate a first MAC PDU. In an example, the one or morenumerologies/TTIs/transmission durations may not comprise the firstnumerology/TTI/transmission duration. The physical layer may create afirst TB using the first MAC PDU. The wireless device may calculatepower for the first TB using at least the power control commands in theDCI/grant and may map the TB to the resources indicated in the DCI/grantand may transmit the TB. In an example, HARQ entity may handletransmission and/or retransmission of transport blocks on a plurality ofTTIs/transmission durations/numerologies of the first cell comprisingthe first TTI/transmission duration/numerology. In an example, thewireless device may receive a NACK and/or a second DCI/grant indicatingretransmission of the first TB (or a new redundancy version of the firstTB). In an example, the DCI/grant may indicate the HARQ retransmissionof the first TB on a second TTI/transmission duration/numerology of theplurality of TTIs/transmission durations/numerologies. In an example,the second TTI/transmission duration/numerology may be among the one ormore TTIs/transmission durations/numerologies. The wireless device maytransmit the HARQ retransmission of the first TB e.g., using thetransmission parameters (e.g., resources) indicated in the secondDCI/grant.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signaling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signaling (e.g., PDCCH like signaling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria (e.g., asdescribed in embodiments in this disclosure). In an example, the MACentity may duplicate the PDCP PDUs for a bearer for which theduplication is configured/enabled and may not duplicate PDCP PDUs for abearer for which the duplication is disabled and/or not configured. Inan example, a PDCP PDU and duplicate PDCP PDUs may correspond todifferent RLC entities/logical channels. In an example, a wirelessdevice MAC entity may perform data discard process (e.g., as describedin embodiments in this disclosure). The buffers for logical channelscorresponding to data and duplicate data may have same data. In anexample, the wireless device may receive a plurality of DCIs/grants. Agrant/DCI in the plurality of DCIs/grants may comprise transmissionparameters (e.g., time/frequency resources, HARQ parameters, MCS, powercontrol commands, etc.). In an example, the wireless device may create aplurality of TBs using to the plurality of DCIs/grants. In an example,each of the plurality of TBs may contain data from a logical channel ofthe plurality of logical channels corresponding to a same bearer (e.g.,bearer configured with packet duplication). In an example, a first TB ofthe plurality of TBs may comprise only data from a logical channelcorresponding to the bearer. The wireless device may receive an ACK forother TBs in the plurality of TBs. The wireless device may stoptransmission or retransmission of the first TB. The wireless device mayflush the HARQ buffer corresponding to the first TB.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signaling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signaling (e.g., PDCCH like signaling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria (e.g., asdescribed in embodiments in this disclosure). In an example, the MACentity may duplicate the PDCP PDUs for a bearer for which theduplication is configured/enabled and may not duplicate PDCP PDUs for abearer for which the duplication is disabled and/or not configured. Inan example, a PDCP PDU and duplicate PDCP PDUs may correspond todifferent RLC entities/logical channels. In an example, a wirelessdevice MAC entity may perform data discard process (e.g., as describedin embodiments in this disclosure). The buffers for logical channelscorresponding to data and duplicate data may have same data. In anexample, the wireless device may receive a plurality of DCIs/grants fora same TTI/transmission duration on a plurality of cells. A grant/DCI inthe plurality of DCIs/grants may comprise transmission parameters (e.g.,time/frequency resources, HARQ parameters, MCS, power control commands,etc.). In an example, the wireless device may create a plurality of TBsusing to the plurality of DCIs/grants. In an example, each of theplurality of TBs may contain data from a logical channel of theplurality of logical channels corresponding to a same bearer (e.g.,bearer configured with packet duplication). In an example, a first TB ofthe plurality of TBs may comprise only data from a logical channelcorresponding to the bearer. The wireless device calculate power for theplurality of TBs at least using the power control commands indicated inthe plurality of DCIs/grants. In an example, the wireless device maydrop the first TB if the wireless is power limited e.g., if the totalcalculated power is larger than the UE maximum transmit power.

Example embodiments enhance the efficiency of BSR and PHR reporting whena plurality of MAC entities handle transmission of data from logicalchannels that contain data and duplicate data.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signaling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signaling (e.g., PDCCH like signaling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria (e.g., asdescribed in embodiments in this disclosure). In an example, the MACentity may duplicate the PDCP PDUs for a bearer for which theduplication is configured/enabled and may not duplicate PDCP PDUs for abearer for which the duplication is disabled and/or not configured. Inan example, a PDCP PDU and duplicate PDCP PDUs may correspond todifferent RLC entities/logical channels. In an example, the wirelessdevice may receive one or more DCIs/grants for transmission on one ormore cells e.g., for one or more numerologies/TTIs/transmissiondurations on the one or more cells. In an example, the cells may belongto different cells groups corresponding to different MAC entities. ADCI/grant may indicate the transmission parameters such as resources fortransmission, power control commands, HARQ parameters, modulation andcoding scheme (MCS), etc. The wireless device may perform a logicalchannel prioritization/multiplexing procedure and may allocate theresources of the grant/DC to one or more logical channels to create aMAC PDU. In an example, the one or more logical channels may compriselogical channels with data and/or duplicate data. In an example, the MAClayer may deliver the MAC PDU to Physical layer to create a transportblock (TB). The wireless device may calculate transmission power for theTB using at least the power control commands in the grant/DCI. ThePhysical layer may map the TB to the time/frequency resources indicatedin the DCI/grant and may transmit the TB. In an example a plurality ofMAC entities may be configured for the plurality of logical channelscorresponding to data and duplicate PDCP PDUs for a bearer configuredwith packet duplication. In an example, the base station may configure aplurality of cells for the wireless device. In an example, the basestation may configure a cell of the plurality of cells to one of aplurality of cells groups. In an example, a cell group may be configuredthat handle transmission and retransmission of logical channelscomprising PDCP PDUs. In an example, a cell group may be configured thathandle transmission and retransmission of duplicate PDCP PDUs. In anexample, the wireless device may transmit a plurality of BSRscorresponding to the plurality of MAC entities to the base station, eachBSR comprising buffer status for logical channels corresponding tological channels handled by a MAC entity.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signaling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signaling (e.g., PDCCH like signaling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria (e.g., asdescribed in embodiments in this disclosure). In an example, the MACentity may duplicate the PDCP PDUs for a bearer for which theduplication is configured/enabled and may not duplicate PDCP PDUs for abearer for which the duplication is disabled and/or not configured. Inan example, a PDCP PDU and duplicate PDCP PDUs may correspond todifferent RLC entities/logical channels. In an example, the wirelessdevice may receive one or more DCIs/grants for transmission on one ormore cells e.g., for one or more numerologies/TTIs on the one or morecells. In an example, the cells may belong to different cells groupscorresponding to different MAC entities. A DCI/grant may indicate thetransmission parameters such as resources for transmission, powercontrol commands, HARQ parameters, modulation and coding scheme (MCS),etc. The wireless device may perform a logical channelprioritization/multiplexing procedure and may allocate the resources ofthe grant/DC to one or more logical channels to create a MAC PDU. In anexample, the one or more logical channels may comprise logical channelswith data and/or duplicate data. In an example, the MAC layer maydeliver the MAC PDU to Physical layer to create a transport block (TB).The wireless device may calculate transmission power for the TB using atleast the power control commands in the grant/DCI. The Physical layermay map the TB to the time/frequency resources indicated in theDCI/grant and may transmit the TB. In an example a plurality of MACentities may be configured for the plurality of logical channelscorresponding to data and duplicate PDCP PDUs for a bearer configuredwith packet duplication. In an example, the base station may configure aplurality of cells for the wireless device. In an example, the basestation may configure a cell of the plurality of cells to one of aplurality of cells groups. In an example, a cell group may be configuredthat handle transmission and retransmission of logical channelscomprising PDCP PDUs. In an example, a cell group may be configured thathandle transmission and retransmission of duplicate PDCP PDUs. In anexample, the wireless device may transmit a BSR to the base station, theBSR comprising buffer status for logical channels handled by theplurality of MAC entity. The BSR may be used by the plurality of MACentities for scheduling the wireless device.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signaling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signaling (e.g., PDCCH like signaling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria (e.g., asdescribed in embodiments in this disclosure). In an example, the MACentity may duplicate the PDCP PDUs for a bearer for which theduplication is configured/enabled and may not duplicate PDCP PDUs for abearer for which the duplication is disabled and/or not configured. Inan example, a PDCP PDU and duplicate PDCP PDUs may correspond todifferent RLC entities/logical channels. In an example, the wirelessdevice may receive one or more DCIs/grants for transmission on one ormore cells e.g., for one or more numerologies/TTIs on the one or morecells. In an example, the cells may belong to different cells groupscorresponding to different MAC entities. A DCI/grant may indicate thetransmission parameters such as resources for transmission, powercontrol commands, HARQ parameters, modulation and coding scheme (MCS),etc. The wireless device may perform a logical channelprioritization/multiplexing procedure and may allocate the resources ofthe grant/DC to one or more logical channels to create a MAC PDU. In anexample, the one or more logical channels may comprise logical channelswith data and/or duplicate data. In an example, the MAC layer maydeliver the MAC PDU to Physical layer to create a transport block (TB).The wireless device may calculate transmission power for the TB using atleast the power control commands in the grant/DCI. The Physical layermay map the TB to the time/frequency resources indicated in theDCI/grant and may transmit the TB. In an example a plurality of MACentities may be configured for the plurality of logical channelscorresponding to data and duplicate PDCP PDUs for a bearer configuredwith packet duplication. In an example, the base station may configure aplurality of cells for the wireless device. In an example, the basestation may configure a cell of the plurality of cells to one of aplurality of cells groups. In an example, a cell group may be configuredthat handle transmission and retransmission of logical channelscomprising PDCP PDUs. In an example, a cell group may be configured thathandle transmission and retransmission of duplicate PDCP PDUs. In anexample, the wireless device may transmit a power headroom report (PHR)corresponding to a grant/DCI received from a MAC entity to the basestation.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signaling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signaling (e.g., PDCCH like signaling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria (e.g., asdescribed in Example A embodiments). In an example, the MAC entity mayduplicate the PDCP PDUs for a bearer for which the duplication isconfigured/enabled and may not duplicate PDCP PDUs for a bearer forwhich the duplication is disabled and/or not configured. In an example,a PDCP PDU and duplicate PDCP PDUs may correspond to different RLCentities/logical channels. In an example, the wireless device mayreceive one or more DCIs/grants for transmission on one or more cellse.g., for one or more numerologies/TTIs/transmission durations on theone or more cells. In an example, the cells may belong to differentcells groups corresponding to different MAC entities. A DCI/grant mayindicate the transmission parameters such as resources for transmission,power control commands, HARQ parameters, modulation and coding scheme(MCS), etc. The wireless device may perform a logical channelprioritization/multiplexing procedure and may allocate the resources ofthe grant/DC to one or more logical channels to create a MAC PDU. In anexample, the one or more logical channels may comprise logical channelswith data and/or duplicate data. In an example, the MAC layer maydeliver the MAC PDU to Physical layer to create a transport block (TB).The wireless device may calculate transmission power for the TB using atleast the power control commands in the grant/DCI. The Physical layermay map the TB to the time/frequency resources indicated in theDCI/grant and may transmit the TB. In an example a plurality of MACentities may be configured for the plurality of logical channelscorresponding to data and duplicate PDCP PDUs for a bearer configuredwith packet duplication. In an example, the base station may configure aplurality of cells for the wireless device. In an example, the basestation may configure a cell of the plurality of cells to one of aplurality of cells groups. In an example, a cell group may be configuredthat handle transmission and retransmission of logical channelscomprising PDCP PDUs. In an example, a cell group may be configured thathandle transmission and retransmission of duplicate PDCP PDUs. In anexample, the wireless device may transmit a power headroom report (PHR)corresponding to a grant/DCI received from any MAC entity to the basestation.

In an example embodiment, uplink PDCP duplication may be configurableper data radio bearer (DBR). In an example, uplink PDCP duplication maybe configurable per signaling radio bearer (SRB), e.g., for the NR-NRdual connectivity (DC) case. In an example, configuration of the uplinkPDCP duplication may be using at least one or more radio resourcecontrol (RRC) configuration messages. In an example, some of the PDCPduplication parameters may be configured using RRC and some of the PDCPduplication parameters may be indicated using at least one MAC controlelement (MAC CE) and/or physical layer signaling (e.g., PDCCH and/oralike). In an example, the initial state of the uplink PDCP duplicationfor a radio bearer may be indicated to the wireless device (e.g., usingan RRC IE and/or MAC CE and/or alike). The initial state may be activeand/or not-active. In an example, the PDCP duplication may be activeupon configuration of PDCP duplication (e.g., upon RRC configuration).In an example, the PDCP duplication may be active upon configuration ofPDCP duplication and may be stopped upon an indication of stopping ofthe PDCP duplication (e.g., with RRC reconfiguration message and/or MACCE and/or physical layer signaling). In an example, the additional legfor transmission of a duplicate packet (e.g., additional carrier towhich a duplicate logical channel corresponding to the duplicate PDCPpackets may be mapped to) may be indicated to the wireless device (e.g.,using an RRC IE and/or MAC CE and/or alike). In an example, the initialstate of the uplink PDCP duplication may be a default state and/orpre-configured state (e.g., active state or not-active state). Theadditional leg for transmission of a duplicate packet may be a defaultleg and/or pre-configured leg (e.g., a default/pre-configured carrierfor transmission of a duplicate logical channel).

In an example embodiment, one or more MAC layer mechanisms may be usedto control PDCP duplication, e.g., to start and/or stop PDCP duplicationfor one or more radio bearers, to indicate additional leg/carrier fortransmission of duplicate PDCP packets e.g., duplicate logicalchannel(s) to which duplicate PDCP packets are mapped to, etc. In anexample, the one or more MAC layer mechanisms may be in combination withother signaling mechanism (e.g., RRC signaling), for controlling thePDCP duplication. In an example, the one or more MAC layer mechanism maybe used for quicker signaling and/or less signaling overhead compared toother signaling mechanisms such as RRC to control the PDCP duplication.In an example, the one or more MAC layer mechanisms may comprisetransmission of at least one MAC control element (MAC CE). Othersignaling mechanisms (e.g., physical layer such as PDCCH or PDCCH likesignaling) may be used in combination with MAC CE and/or RRC and/oralone to control the PDCP duplication.

In an example embodiment, a base station may use at least one MACcontrol element (MAC CE) to control (e.g., in combination with othersignaling mechanisms such as RRC and/or alone) uplink PDCP duplication.In an example, controlling the PDCP duplication may comprise startingand/or stopping the duplication for one or more radio bearers,indicating the additional leg(s) for transmission of at least one PDCPduplicate packet and/or logical channel that PDCP duplicate packets aremapped to, the carrier(s) to transmit duplicate logical channel(s)corresponding to duplicate PDCP packets, logical channel correspondingto PDCP PDUs and/or duplicate logical channels corresponding toduplicate PDCP PDUs, one or more parameters corresponding to duplicatedata transmission, etc.

In an example, duplicate PDCP packet data units (PDUs) may be submittedto two different RLC entities (e.g., a first RLC entity and a second RLCentity). In an example, the first RLC entity may be mapped to a firstlogical channel. The second RLC entity (e.g., the RLC entity receivingthe duplicate PDCP PDUs) may be mapped to a second logical channel.

In an example embodiment, a wireless device may receive one or moremessages comprising configuration parameters for a plurality of cells.In an example, the one or more messages may comprise one or more RRCmessages. In an example, the configuration parameters may compriseparameters for a plurality of logical channels. In an example, theconfiguration parameters may comprise parameters for one or more radiobearers. In an example, the configuration parameters may indicatewhether PDCP duplication is configured and/or activated/started for afirst radio bearer. In an example, RRC may configure PDCP duplicationfor the first radio bearer and MAC CE and/or other MAC layer and/orphysical layer signaling may activate/start the PDCP duplication for thefirst radio bearer. In an example, the first radio bearer may be mappedto a first logical channel and a second logical channel. In an example,the one or more messages may indicate the first logical channel and thesecond logical channel. In an example, the one or more messages maycomprise a field indicating the first logical channel (e.g., comprisinga first logical channel ID) and the second logical channel (e.g.,comprising a second logical channel ID). In an example, the firstlogical channel may comprise data corresponding to PDCP PDUscorresponding to the first radio bearer. The second logical channel maycomprise data corresponding to duplicate PDCP PDUs corresponding to thefirst radio bearer. In an example, the one or more messages may indicatethat the first logical channel is mapped to at least one firstcell/carrier and the second logical channel is mapped to at least onesecond cell/carrier. The at least one first cell/carrier and the atleast one second cell/carrier may be different. In an example, themapping of the first logical channel and/or the second logical channelto cells/carriers (e.g., the at least one first cell/carrier and the atleast one second cell/carrier) may change. In an example, MAC CE may beused to indicate and/or update the mapping of the first logical channelto the at least one first cell/carrier and/or the second logical channelto the at least one second cell/carrier. In an example, MAC CE maycomprise a field that indicates the mapping of the first logical channelto the at least one first cell/carrier and the mapping of the secondlogical channel to the at least one second cell/carrier.

In an example embodiment, in response to starting and/or activating PDCPduplication for the radio bearer (e.g., in response to RRC configurationand/or activation with MAC CE and/or activation with physical layersignaling), the MAC entity may copy the content of buffers associatedwith the first logical channel (e.g., MAC layer buffer(s) and/or RLClayer buffer(s) and/or alike) to the buffers associated with the secondlogical channel and may start applying the mapping restriction for thefirst logical channel (e.g., mapping of the first logical channel to theat least one first cell/carrier) and the second logical channel (e.g.,mapping of the second logical channel to the at least one secondcell/carrier) in response to performing the logical channelprioritization (LCP) procedure.

In an example embodiment, in response to starting and/or activating PDCPduplication for the radio bearer, the MAC entity may continuetransmitting data in buffers associated with the first logical channelwithout applying the mapping restriction (e.g., mapping of the firstlogical channel to the at least one first cell/carrier) in response toperforming the LCP procedure. The PDCP layer may submit the PDCP packetsand duplicate PDCP packets to two different RLC entities (e.g.,corresponding to the first logical channel and the second logicalchannel). In an example, in response to data in buffer(s) associatedwith the first logical channel being exhausted/depleted, the RLC entitycorresponding to the first logical channel may submit data in itsassociated buffer(s) to the MAC layer and/or the RLC entitycorresponding to the second logical channel may submit data in itsassociated buffer(s) to the MAC layer.

In an example embodiment, in response to stopping and/or deactivatingPDCP duplication for the radio bearer (e.g., stopping/deactivating usingMAC CE and/or RRC reconfiguration and/or alike), the mapping restrictionfor the first logical channel (e.g., mapping of the first logicalchannel to the at least one first cell/carrier) may stop (e.g., may nolonger be applied and/or the mapping restriction may not be used inperforming the logical channel prioritization procedure). In an example,in response to stopping and/or deactivating the PDCP duplication for theradio bearer, the second logical channel may be dismantled/deactivated.In an example, in response to the stopping and/or deactivating the PDCPduplication for the radio bearer, PDCP layer may not submit multiplePDCP packets to the RLC layer.

In an example embodiment, in response to the stopping and/ordeactivating the PDCP duplication for the radio bearer, data in buffersassociated with the second logical channel may be discarded/flushedand/or the second logical channel may be dismantled/deactivated. The LCPprocedure may not consider the mapping restriction between the first andthe second logical channel to the at least one first cell/carrier andthe at least one second cell/carrier. In an example, in response to thestopping and/or deactivating the PDCP duplication for the radio bearer,a MAC entity may continue transmitting data in buffers associated withthe second logical channel and/or the LCP procedure may continue toconsider the mapping restriction between the first logical channel tothe at least one first cell/carrier and the second logical channel tothe at least one second cell/carrier until the data in buffersassociated with the second logical channel is exhausted/depleted. Inresponse to the data in buffers associated with the second logicalchannel being exhausted/depleted, the second logical channel may bedismantled/deactivated and/or the LCP procedure may not consider themapping restriction between the first and the second logical channel tothe at least one first cell/carrier and the at least one secondcell/carrier.

In example embodiment, a logical channel may be configured with mappingrestrictions. The wireless device may apply mapping restrictions to thelogical channel so that data from the logical channel may be transmittedvia one or more cells in a plurality of cells. In an example, the datafrom the logical channel may not be transmitted via other cells than theone or more cells in the plurality of cell. Other logical channelmapping restrictions may be configured/applied. For example, the logicalchannel may be transmitted via one or more subcarrier spacings in aplurality of subcarrier spacings or the logical channel may betransmitted via transport blocks that lead to transmission durations(e.g., PUSCH durations) less than a maximum transmission duration. Forexample, to achieve QoS requirements of a first logical channel (e.g.,URLLC), uplink resource used for transmission of data from the firstlogical channel may be limited to one or more first cells and/or one ormore first subcarrier spacings. In an example, the transmission durationof a transport block comprising the data from the first logical channelmay be less than one or more first transmission durations. A secondlogical channel (e.g., corresponding to voice) may be configured with adifferent mapping restriction. A third logical channel may not beconfigured with a mapping restriction. The configuration of mappingrestriction for logical channels helps to achieve the QoS requirementsof the configured logical channels.

In an example implementation of mapping restriction, a logical channelcorresponding to a bearer configured with duplication may be configuredwith mapping restriction. A base station may configure PDCP packetduplication for a bearer of wireless device. Existing implementation ofactivation/deactivation of packet duplication, leads to inefficientutilization of uplink resources when logical channel mappingrestrictions is configured. There is a need to enhance existing packetduplication procedure to enhance uplink resource utilization as thebearers configured with duplication are dynamically activated anddeactivated. Example embodiments enhance the existing packet duplicationprocedures and logical channel mapping restriction processes. Exampleembodiments implements cross-layer optimization to certain logicalchannels to achieve higher quality of service.

Example embodiments are shown in FIG. 25 and FIG. 26. A wireless devicemay receive configuration parameters comprising a parameter indicatingthat uplink duplication is configured for a bearer. In an example, theuplink duplication may be uplink PDCP packet duplication. Theduplication may be used to enhance the reliability and latency of datapackets corresponding to the bearer. In an example, the configurationparameters for the bearer may comprise the parameter. The bearer maycorrespond to a first logical channel and a second logical channel. Inan example, the bearer may correspond to a first RLC entitycorresponding to the first logical channel and a second RLC entitycorresponding to the second logical channel. The first RLC entity mayhandle transmission of original PDCP packets of the bearer. One or morefirst buffers associated with the first logical channel may comprise theoriginal PDCP packets of the bearer. The second RLC entity may handletransmission of duplicate PDCP packets of the bearer. One or more secondbuffers associated with the second logical channel may comprise theduplicate PDCP packets of the bearer. The configuration parameters mayindicate first mapping restrictions of the first logical channel to atleast one first cell. In an example, configuration parameters of thefirst logical channel may indicate the first mapping restriction. In anexample, the configuration parameters of the first logical channel mayindicate the at least one first cell (e.g., cell ID of the at least onefirst cell). The configuration parameters may indicate second mappingrestrictions of the second logical channel to at least one second cell.In an example, configuration parameters of the second logical channelmay indicate the second mapping restriction. In an example, theconfiguration parameters of the second logical channel may indicate theat least one second cell (e.g., cell ID of the at least one secondcell).

In an example, the wireless device may receive a control elementindicating activation or deactivation of duplication for the bearer. Inan example, the control element may be a MAC control element. In anexample, the control element may comprise one or more fields indicatingactivation and/or deactivation of one or more bearers comprising thebearer. In an example, a value of zero of a field in the one or fieldsmay indicate that duplication is deactivated for a corresponding bearer.In an example, a value of one of a field in the one or more fields mayindicate that duplication is activated for a corresponding bearer. In anexample, if the control element indicates activation of the duplicationfor the bearer (e.g., if a field corresponding to the bearer in the oneor more fields of the control element has a value of one), the wirelessdevice may apply the first mapping restrictions to the first logicalchannel and the second mapping restrictions to the second logicalchannel. By applying the first mapping restrictions and the secondmapping restrictions and by transmitting both original packetscorresponding to the bearer and duplicate packets corresponding to thebearer, the uplink reliability and latency are improved for the bearer.In an example, if the control element indicates deactivation of theduplication for the bearer (e.g., if a field corresponding to the bearerin the one or more fields of the control element has a value of one),the wireless device may lift the first mapping restrictions to the firstlogical channel and the second mapping restrictions to the secondlogical channel. The lifting of the first mapping restrictions and thesecond mapping restrictions, if duplication is deactivated for thebearer, provides more scheduling flexibility and enables the wirelessdevice to employ uplink resources for transmission of data which are notallowed to be used when duplication is activated. This improves uplinkresource utilization efficiency and enhances the network performance.

In an example, the wireless device may receive a downlink controlinformation (DCI), e.g., in a PDCCH. The DCI may comprise an uplinkgrant for the wireless device. The uplink grant may indicatetransmission parameters for one or more transport blocks (TBs). Thetransmission parameters may comprise uplink resources for transmissionof the one or more TBs, power control command, MIMO parameters, HARQparameters, etc. In an example, a multiplexing and assembling entity inthe MAC entity may construct the one or more TBs. The multiplexing andassembling entity may perform a logical channel prioritizationprocedure, considering the mapping restrictions. The wireless device maytransmit the one or more TBs using the uplink resources indicated by theuplink grant.

In on embodiment, in response to RRC configuration and/or activation ofPDCP duplication (e.g., by MAC layer) for a radio bearer, PHR istriggered so that base station knows if UE is power limited for a cell.If duplication is used for URLLC and the logical channel or theduplicate logical channel are mapped to a cell which is power limited,the benefit of duplication is diminished. The base station may use thePHR to configure the logical channel and the duplicate logical channelto be mapped to cells that are not power limited. In one embodiment, thePHR timers (e.g., periodicPHR-Timer) may be have different values ifduplication is triggered compared to when duplication is not triggered.

In an example, a wireless device may use Power Headroom reporting (PHR)procedure to provide a serving base station with information about thedifference between a nominal UE maximum transmit power and an estimatedpower for uplink (e.g., UL-SCH) transmission and/or SRS transmission peractivated Serving Cell and/or with information about the differencebetween the nominal UE maximum power and an estimated power for UL-SCHand physical uplink control channel (e.g., PUCCH) transmission (e.g., onSpCell and PUCCH SCell). In an example, RRC may control Power Headroomreporting by configuring a plurality of parameters, e.g., one or moretimers (e.g., periodicPHR-Timer, prohibitPHR-Timer and/or alike), and/ora parameter that sets the change in a measured downlink pathloss (e.g.,dl-PathlossChange and/or alike), and/or the required power backoff dueto power management, etc. In an example, the PHR may be triggered inresponse to occurrence of an event in a plurality of events occurring.In an example, the plurality of events may comprise: theperiodicPHR-Timer expiring or the periodicPHR-Timer being expired andpath loss having changed more than dl-pathlossChange dB for at least oneactivated serving cell of a MAC entity which may be used as a pathlossreference since the last transmission of a PHR in the MAC entity whenthe MAC entity has uplink resources for new transmission,periodicPHR-Timer being expired, in response to configuration and/orreconfiguration of the power headroom reporting functionality by upperlayers which is not used to disable the function, in response toactivation of an SCell of a MAC entity with configured uplink, etc.

In an example embodiment, a wireless device may receive one or moremessages comprising configuration parameters for a plurality of cells.In an example, the one or more messages may comprise one or more RRCmessages. In an example, the configuration parameters may compriseparameters for a plurality of logical channels. In an example, theconfiguration parameters may comprise parameters for one or more radiobearers. In an example, the configuration parameters may indicatewhether PDCP duplication is configured and/or activated/started for afirst radio bearer. In an example, RRC may configure PDCP duplicationfor the first radio bearer and MAC CE and/or other MAC layer and/orphysical layer signaling may activate/start the PDCP duplication for thefirst radio bearer. In an example, RRC may configure and activate/startPDCP duplication for the first radio bearer. In an example, the PDCPduplication for the first radio bearer may start/be activated inresponse to RRC configuration. In an example, the first radio bearer maybe mapped to a first logical channel and a second logical channel. In anexample, the one or more messages may indicate the first logical channeland the second logical channel. In an example, the one or more messagesmay comprise a field indicating the first logical channel (e.g.,comprising a first logical channel ID) and the second logical channel(e.g., comprising a second logical channel ID). In an example, the MACCE may indicate the first logical channel and the second logicalchannel. In an example, the MAC CE may comprise a field indicating thefirst logical channel (e.g., comprising a first logical channel ID) andthe second logical channel (e.g., comprising a second logical channelID). In an example, the buffers associated with the first logicalchannel may comprise data corresponding to PDCP PDUs corresponding tothe first radio bearer. The buffers associated with the second logicalchannel may comprise data corresponding to duplicate PDCP PDUscorresponding to the first radio bearer. In an example, the one or moremessages may indicate that the first logical channel is mapped to one ormore first cells/carriers and the second logical channel is mapped toone or more second cells/carriers. In an example, the MAC CE mayindicate that the first logical channel is mapped to one or more firstcells/carriers and the second logical channel is mapped to one or moresecond cells/carriers. In an example, the MAC CE may comprise a fieldindicating the one or more first cells (e.g., using one or more firstcell IDs) and the one or more second cells (e.g., using one or moresecond cell IDs). In an example, a MAC entity in the wireless device mayconsider the mapping of the first logical channel to the one or morefirst cells/carriers and the second logical channel to the one or moresecond cells/carriers in response to performing a logical channelprioritization procedure. In an example, the MAC entity in the wirelessdevice may trigger a power headroom report (PHR) in response toconfiguration and/or activation of PDCP duplication of one or more radiobearers for the wireless device. In an example, the MAC entity in thewireless device may trigger a PHR in response to receiving anactivation/starting command (e.g., a MAC CE and/or an RRC messageconfiguring/reconfiguring/starting PDCP duplication) from the basestation to configure and/or active/start PDCP duplication for one ormore radio bearers. In an example, the PHR MAC CE in response to the PHRbeing triggered by the configuring/reconfiguring/starting of PDCPduplication may have a first format (e.g., a short format, etc.). Thefirst format may be different from one or more PHR formats when the PHRis triggered by one or more other events. In an example, the PHR MAC CEin response to PHR being triggered by theconfiguring/reconfiguring/starting PDCP duplication may comprise one ormore first PHR types. The one or more first PHR types may be differentfrom one or more second PHR types in response to PHR being triggered byone or more other events. In an example, the wireless device may receivea downlink control information (DCI), e.g., in a PDCCH. The DCI maycomprise an uplink grant for the wireless device. The uplink grant mayindicate transmission parameters for one or more transport blocks (TBs).The transmission parameters may comprise uplink resources fortransmission of the one or more TBs, power control command, MIMOparameters, HARQ parameters, etc. In an example, a multiplexing andassembling entity in the MAC entity may multiplex the PHR MAC CE in theone or more TBs. The multiplexing and assembling entity may perform alogical channel prioritization procedure and multiplex a PHR MAC CE withMAC SDUs. The wireless device may transmit the one or more TBs using theuplink resources indicated by the uplink grant.

In an example embodiment, a wireless device may receive one or moremessages comprising configuration parameters for a plurality of cells.In an example, the one or more messages may comprise one or more RRCmessages. In an example, the configuration parameters may compriseparameters for a plurality of logical channels. In an example, theconfiguration parameters may comprise parameters for one or more radiobearers. In an example, the configuration parameters may indicatewhether PDCP duplication is configured and/or activated/started for afirst radio bearer. In an example, RRC may configure PDCP duplicationfor the first radio bearer and MAC CE and/or other MAC layer and/orphysical layer signaling may activate/start the PDCP duplication for thefirst radio bearer. In an example, RRC may configure and activate/startPDCP duplication for the first radio bearer. In an example, the PDCPduplication for the first radio bearer may start/be activated inresponse to RRC configuration. In an example, the first radio bearer maybe mapped to a first logical channel and a second logical channel. In anexample, the one or more messages may indicate the first logical channeland the second logical channel. In an example, the one or more messagesmay comprise a field indicating the first logical channel (e.g.,comprising a first logical channel ID) and the second logical channel(e.g., comprising a second logical channel ID). In an example, the MACCE may indicate the first logical channel and the second logicalchannel. In an example, the MAC CE may comprise a field indicating thefirst logical channel (e.g., comprising a first logical channel ID) andthe second logical channel (e.g., comprising a second logical channelID). In an example, the buffers associated with the first logicalchannel may comprise data corresponding to PDCP PDUs corresponding tothe first radio bearer. The buffers associated with the second logicalchannel may comprise data corresponding to duplicate PDCP PDUscorresponding to the first radio bearer. In an example, the one or moremessages may indicate that the first logical channel is mapped to one ormore first cells/carriers and the second logical channel is mapped toone or more second cells/carriers. In an example, the MAC CE mayindicate that the first logical channel is mapped to one or more firstcells/carriers and the second logical channel is mapped to one or moresecond cells/carriers. In an example, the MAC CE may comprise a fieldindicating the one or more first cells (e.g., using one or more firstcell IDs) and the one or more second cells (e.g., using one or moresecond cell IDs). In an example, a MAC entity in the wireless device mayconsider the mapping of the first logical channel to the one or morefirst cells/carriers and the second logical channel to the one or moresecond cells/carriers in response to performing a logical channelprioritization procedure. In an example, the configuration parametersmay comprise parameters for a timer. The parameters for the timer maycomprise a first timer value and a second timer value. The wirelessdevice may use the first timer value in response to PDCP duplicationbeing configured and/or activated/started for the wireless device. Thewireless device may use the second timer value in response to PDCPduplication not being configured and/or activated/started for thewireless device. In an example, the wireless device may start the timerin response to MAC entity having uplink resources allocated for newtransmission for a TTI and it being the first UL resource allocated fora new transmission since last MAC reset. In an example, a MAC entity maystart the timer in response to transmission of a PHR MAC CE. Otherevents may start the timer. The wireless may trigger a PHR in responseto the timer being expired. In an example, the wireless device may nottrigger a PHR in response to the timer being running. In an example, thetimer may be a periodicPHR-Timer. In an example, the timer may be aprohibitPHR-timer. In an example, the wireless device may receive adownlink control information (DCI), e.g., in a PDCCH. The DCI maycomprise an uplink grant for the wireless device. The uplink grant mayindicate transmission parameters for one or more transport blocks (TBs).The transmission parameters may comprise uplink resources fortransmission of the one or more TBs, power control command, MIMOparameters, HARQ parameters, etc. In an example, a multiplexing andassembling entity in the MAC entity may multiplex the PHR MAC CE in theone or more TBs. The multiplexing and assembling entity may perform alogical channel prioritization procedure and multiplex a PHR MAC CE withMAC SDUs. The wireless device may transmit the one or more TBs using theuplink resources indicated by the uplink grant.

If a logical channel and/or its duplicate cannot be transmitted on acell due to poor channel condition, the corresponding logical channelbuffer occupancy will be very large. The base station needs to know thisto configure/reconfigure the cells associated with logical channels andtheir duplicates. In on embodiment, in response to RRC configurationand/or activation of PDCP duplication (e.g., by MAC layer) for a radiobearer, BSR is triggered. If duplication is used for URLLC and thelogical channel or the duplicate logical channel are mapped to a cellwhich has poor channel conditions, the benefit of duplication isdiminished. The base station may use the BSR to configure/reconfigurethe logical channel and the duplicate logical channel to be mapped tocells with good channel conditions. In one embodiment, the BSR timers(e.g., periodicBSR-Timer) may be have different values if duplication istriggered compared to when duplication is not triggered.

The Buffer Status reporting (BSR) procedure may be used to provide aserving base station with information about the amount of data availablefor transmission in UL buffers associated with a MAC entity. RRC maycontrol BSR by configuring a plurality of timers (e.g.,periodicBSR-Timer and/or retxBSR-Timer and/orlogicalChannelSR-ProhibitTimer, etc.). In an example, a logical channelmay be configured with a logicalChannelGroup parameter which mayallocate the logical channel to a logical channel group (LCG). A BSR maybe triggered in response to an event in a plurality of events occurring.

In an example embodiment, a wireless device may receive one or moremessages comprising configuration parameters for a plurality of cells.In an example, the one or more messages may comprise one or more RRCmessages. In an example, the configuration parameters may compriseparameters for a plurality of logical channels. In an example, theconfiguration parameters may comprise parameters for one or more radiobearers. In an example, the configuration parameters may indicatewhether PDCP duplication is configured and/or activated/started for afirst radio bearer. In an example, RRC may configure PDCP duplicationfor the first radio bearer and MAC CE and/or other MAC layer and/orphysical layer signaling may activate/start the PDCP duplication for thefirst radio bearer. In an example, RRC may configure and activate/startPDCP duplication for the first radio bearer. In an example, the PDCPduplication for the first radio bearer may start/be activated inresponse to RRC configuration. In an example, the first radio bearer maybe mapped to a first logical channel and a second logical channel. In anexample, the one or more messages may indicate the first logical channeland the second logical channel. In an example, the one or more messagesmay comprise a field indicating the first logical channel (e.g.,comprising a first logical channel ID) and the second logical channel(e.g., comprising a second logical channel ID). In an example, the MACCE may indicate the first logical channel and the second logicalchannel. In an example, the MAC CE may comprise a field indicating thefirst logical channel (e.g., comprising a first logical channel ID) andthe second logical channel (e.g., comprising a second logical channelID). In an example, the buffers associated with the first logicalchannel may comprise data corresponding to PDCP PDUs corresponding tothe first radio bearer. The buffers associated with the second logicalchannel may comprise data corresponding to duplicate PDCP PDUscorresponding to the first radio bearer. In an example, the one or moremessages may indicate that the first logical channel is mapped to one ormore first cells/carriers and the second logical channel is mapped toone or more second cells/carriers. In an example, the MAC CE mayindicate that the first logical channel is mapped to one or more firstcells/carriers and the second logical channel is mapped to one or moresecond cells/carriers. In an example, the MAC CE may comprise a fieldindicating the one or more first cells (e.g., using one or more firstcell IDs) and the one or more second cells (e.g., using one or moresecond cell IDs). In an example, a MAC entity in the wireless device mayconsider the mapping of the first logical channel to the one or morefirst cells/carriers and the second logical channel to the one or moresecond cells/carriers in response to performing a logical channelprioritization procedure. In an example, the MAC entity in the wirelessdevice may trigger a buffer status report (BSR) in response toconfiguration and/or activation of PDCP duplication of one or more radiobearers for the wireless device. In an example, the MAC entity in thewireless device may trigger a BSR in response to receiving anactivation/starting command (e.g., a MAC CE and/or an RRC messageconfiguring/reconfiguring/starting PDCP duplication) from the basestation to configure and/or active/start PDCP duplication for one ormore radio bearers. In an example, the BSR MAC CE in response to the BSRbeing triggered by the configuring/reconfiguring/starting of PDCPduplication may have a first format (e.g., a short format, etc.). Thefirst format may be different from one or more BSR formats when the BSRis triggered by one or more other events. In an example, the wirelessdevice may receive a downlink control information (DCI), e.g., in aPDCCH. The DCI may comprise an uplink grant for the wireless device. Theuplink grant may indicate transmission parameters for one or moretransport blocks (TB s). The transmission parameters may comprise uplinkresources for transmission of the one or more TBs, power controlcommand, MIMO parameters, HARQ parameters, etc. In an example, amultiplexing and assembling entity in the MAC entity may multiplex theBSR MAC CE in the one or more TBs. The multiplexing and assemblingentity may perform a logical channel prioritization procedure andmultiplex a BSR MAC CE with MAC SDUs. The wireless device may transmitthe one or more TBs using the uplink resources indicated by the uplinkgrant.

In an example embodiment, a wireless device may receive one or moremessages comprising configuration parameters for a plurality of cells.In an example, the one or more messages may comprise one or more RRCmessages. In an example, the configuration parameters may compriseparameters for a plurality of logical channels. In an example, theconfiguration parameters may comprise parameters for one or more radiobearers. In an example, the configuration parameters may indicatewhether PDCP duplication is configured and/or activated/started for afirst radio bearer. In an example, RRC may configure PDCP duplicationfor the first radio bearer and MAC CE and/or other MAC layer and/orphysical layer signaling may activate/start the PDCP duplication for thefirst radio bearer. In an example, RRC may configure and activate/startPDCP duplication for the first radio bearer. In an example, the PDCPduplication for the first radio bearer may start/be activated inresponse to RRC configuration. In an example, the first radio bearer maybe mapped to a first logical channel and a second logical channel. In anexample, the one or more messages may indicate the first logical channeland the second logical channel. In an example, the one or more messagesmay comprise a field indicating the first logical channel (e.g.,comprising a first logical channel ID) and the second logical channel(e.g., comprising a second logical channel ID). In an example, the MACCE may indicate the first logical channel and the second logicalchannel. In an example, the MAC CE may comprise a field indicating thefirst logical channel (e.g., comprising a first logical channel ID) andthe second logical channel (e.g., comprising a second logical channelID). In an example, the buffers associated with the first logicalchannel may comprise data corresponding to PDCP PDUs corresponding tothe first radio bearer. The buffers associated with the second logicalchannel may comprise data corresponding to duplicate PDCP PDUscorresponding to the first radio bearer. In an example, the one or moremessages may indicate that the first logical channel is mapped to one ormore first cells/carriers and the second logical channel is mapped toone or more second cells/carriers. In an example, the MAC CE mayindicate that the first logical channel is mapped to one or more firstcells/carriers and the second logical channel is mapped to one or moresecond cells/carriers. In an example, the MAC CE may comprise a fieldindicating the one or more first cells (e.g., using one or more firstcell IDs) and the one or more second cells (e.g., using one or moresecond cell IDs). In an example, a MAC entity in the wireless device mayconsider the mapping of the first logical channel to the one or morefirst cells/carriers and the second logical channel to the one or moresecond cells/carriers in response to performing a logical channelprioritization procedure. In an example, the configuration parametersmay comprise parameters for a timer. The parameters for the timer maycomprise a first timer value and a second timer value. The wirelessdevice may use the first timer value in response to PDCP duplicationbeing configured and/or activated for the wireless device. The wirelessdevice may use the second timer value in response to PDCP duplicationnot being configured and/or activated for the wireless device. In anexample, the wireless device may start the timer in response togenerating one or more BSR MAC CEs. In an example, the wireless devicemay start the timer in response to generating one or more BSR MAC CEsexcept when generated BSRs are Truncated BSRs. The timer may be startedin response to other events. The wireless device may trigger a BSR inresponse to the timer being expired. In an example, the timer may be aperiodicBSR-Timer. In an example, the timer may be a retxBSR-Timer. Inan example, the timer may be a logicalChannelSR-ProhibitTimer. In anexample, the wireless device may receive a downlink control information(DCI), e.g., in a PDCCH. The DCI may comprise an uplink grant for thewireless device. The uplink grant may indicate transmission parametersfor one or more transport blocks (TBs). The transmission parameters maycomprise uplink resources for transmission of the one or more TBs, powercontrol command, MIMO parameters, HARQ parameters, etc. In an example, amultiplexing and assembling entity in the MAC entity may multiplex theBSR MAC CE in the one or more TBs. The multiplexing and assemblingentity may perform a logical channel prioritization procedure andmultiplex a BSR MAC CE with MAC SDUs. The wireless device may transmitthe one or more TBs using the uplink resources indicated by the uplinkgrant.

The PDCP duplication control MAC CE is a downlink MAC CE used by thebase station to control the PDCP duplication function for one or moreradio bearers configured for a wireless device. In an example, the PDCPduplication control MAC CE may start/stop the PDCP duplication for oneor more radio bearers. The one or more radio bearers may have beenconfigured by RRC for PDCP duplication. In an example, part of PDCPduplication parameters for a radio bearer may be configured by RRC andpart of the parameters may be indicated using the PDCP duplicationcontrol MAC CE. In an example, part of the PDCP duplication parametersmay be updated with the PDCP duplication control MAC CE after beingconfigured by RRC. Example PDCP duplication parameters that may beindicated by the MAC CE may be the cells that logical channelscorresponding to a radio bearer configured with PDCP are mapped to,logical channels that the radio bearer configured with PDCP duplicationare mapped to, etc.

In an example embodiment, a wireless device may receive one or moremessages comprising configuration parameters for a plurality of cells.In an example, the one or more messages may comprise one or more RRCmessages. In an example, the configuration parameters may compriseparameters for one or more logical channels. In an example, theconfiguration parameters may comprise parameters for one or more radiobearers. In an example, the configuration parameters may indicatewhether PDCP duplication is configured for one or more first radiobearers. In an example, RRC may configure PDCP duplication for the oneor more first radio bearers. MAC CE may activate/start and/ordeactivate/stop the PDCP duplication for the one or more first radiobearers. The RRC configuration may comprise PDCP duplication parametersfor the one or more first radio bearers. In an example, a radio bearerin the one or more first radio bearers may be mapped to a first logicalchannel and a second logical channel. In an example, the one or moremessages and/or the one or more RRC messages may indicate the firstlogical channel and the second logical channel. The buffers associatedwith the first logical channel may comprise data corresponding to PDCPPDUs corresponding to the radio bearer. The buffers associated withsecond logical channel may comprise data corresponding to duplicate PDCPPDUs corresponding to the radio bearer. In an example, RRC may indicatemapping restriction for the first logical channel and the second logicalchannel. As an example of mapping restriction, RRC may indicate that thefirst logical channel may be mapped to one or more first cells/carriersand the second logical channel may be mapped to one or more secondcells/carriers. In an example, the one or more first cells/carriers andthe one or more second cells/carriers may be different. The wirelessdevice may receive a MAC CE to activate/start and/or deactivate/stop thePDCP duplication for the one or more first radio bearers. In an example,the MAC CE may comprise at least one activation/deactivation bit thatactivates/deactivates PDCP duplication for the one or more first radiobearers. In an example, the MAC CE may comprise a singleactivation/deactivation bit that activates/deactivates PDCP duplicationfor the one or more first radio bearers. In an example, theactivation/deactivation bit may take a value of 1 (e.g., toactivate/start) or 0 (e.g., to deactivate/stop) PDCP duplication for theone or more first radio bearers. In an example, MAC CE may not comprisea payload (e.g., may comprise zero bits). The presence of a MAC PDUsubheader with LCID corresponding to the PDCP duplication control MAC CEmay indicate that PDCP duplication for the one or more first radiobearers are activated. In an example, the wireless device may receive adownlink control information (DCI), e.g., in a PDCCH. The DCI maycomprise an uplink grant for the wireless device. The uplink grant mayindicate transmission parameters for one or more transport blocks (TBs).The transmission parameters may comprise uplink resources fortransmission of the one or more TBs, power control command, MIMOparameters, HARQ parameters, etc. In an example, the MAC entity mayconstruct the one or more TBs. The multiplexing and assembling entitymay perform a logical channel prioritization procedure and multiplex MACSDUs and/or MAC CEs. The wireless device may transmit the one or moreTBs using the uplink resources indicated by the uplink grant.

In an example embodiment, a wireless device may receive one or moremessages comprising configuration parameters for a plurality of cells.In an example, the one or more messages may comprise one or more RRCmessages. In an example, the configuration parameters may compriseparameters for one or more logical channels. In an example, theconfiguration parameters may comprise parameters for one or more radiobearers. In an example, the configuration parameters may indicatewhether PDCP duplication is configured for one or more first radiobearers. In an example, RRC may configure PDCP duplication for the oneor more first radio bearers. MAC CE may activate/start and/ordeactivate/stop the PDCP duplication for one or more second radiobearers of the one or more first radio bearers. The one or more secondradio beaeres may be a subset of the one or more first radio bearers.The RRC configuration may comprise PDCP duplication parameters for theone or more first radio bearers. In an example, a radio bearer in theone or more first radio bearers may be mapped to a first logical channeland a second logical channel. In an example, the one or more messagesand/or the one or more RRC messages may indicate the first logicalchannel and the second logical channel. The buffers associated with thefirst logical channel may comprise data corresponding to PDCP PDUscorresponding to the radio bearer. The buffers associated with thesecond logical channel may comprise data corresponding to duplicate PDCPPDUs corresponding to the radio bearer. In an example, RRC may indicatemapping restriction for the first logical channel and the second logicalchannel. As an example of mapping restriction, RRC may indicate that thefirst logical channel may be mapped to one or more first cells/carriersand the second logical channel may be mapped to one or more secondcells/carriers. In an example, the one or more first cells/carriers andthe one or more second cells/carriers may be different. The wirelessdevice may receive a MAC CE to activate/start and/or deactivate/stop thePDCP duplication for the one or more second logical channels of the oneor more first radio bearers. In an example, the MAC CE may comprise afield that activates/starts and/or deactivates/stops PDCP duplicationfor the one or more second radio bearers. In an example, the field maycomprise a bitmap indicating the one or more second radio bearers in theone or more first radio bearers. In an example, the MAC CE may compriseIDs corresponding to the one or more second radio bearers indicatingPDCP duplication for the one or more second radio bearers areactivated/started and/or deactivated/stopped. In an example, the PDCPduplication control MAC CE may comprise a first format (e.g., comprisingone octet) or a second format (e.g., comprising a plurality of octetse.g., 2, 3, 4, etc.). The format of the PDCP duplication MAC CE that isused by the base station may depend on the number of radio bearers thatare configured (e.g., with RRC) for PDCP duplication (e.g., the numberof the one or more first radio bearers). In an example, the PDCPduplication control MAC CE may comprise of one format (e.g., the firstformat). In an example, the wireless device may receive a downlinkcontrol information (DCI), e.g., in a PDCCH. The DCI may comprise anuplink grant for the wireless device. The uplink grant may indicatetransmission parameters for one or more transport blocks (TBs). Thetransmission parameters may comprise uplink resources for transmissionof the one or more TBs, power control command, MIMO parameters, HARQparameters, etc. In an example, the MAC entity may construct the one ormore TBs. The multiplexing and assembling entity may perform a logicalchannel prioritization procedure and multiplex MAC SDUs and/or MAC CEs.The wireless device may transmit the one or more TBs using the uplinkresources indicated by the uplink grant.

In an example embodiment, a wireless device may receive one or moremessages comprising configuration parameters for a plurality of cells.In an example, the one or more messages may comprise one or more RRCmessages. In an example, the configuration parameters may compriseparameters for one or more logical channels. In an example, theconfiguration parameters may comprise parameters for one or more radiobearers. In an example, the configuration parameters may indicatewhether PDCP duplication is configured for one or more first radiobearers. In an example, RRC may configure PDCP duplication for the oneor more first radio bearers. MAC CE may activate/start and/ordeactivate/stop the PDCP duplication for the one or more first radiobearers. The RRC configuration may comprise some of the PDCP duplicationparameters for the one or more first radio bearers. The MAC CE maycomprise some of the PDCP duplication parameters for the one or morefirst radio bearers. In an example, a radio bearer in the one or morefirst radio bearers may be mapped to a first logical channel and asecond logical channel. In an example, the one or more messages and/orthe one or more RRC messages may indicate the first logical channel andthe second logical channel. In an example, the MAC CE may indicate thefirst logical channel and the second logical channel. In an example, theMAC CE may comprise a field comprising a first logical channel ID and asecond logical channel ID. The buffers associated with the first logicalchannel may comprise data corresponding to PDCP PDUs corresponding tothe radio bearer. The buffers associated with the second logical channelmay comprise data corresponding to duplicate PDCP PDUs corresponding tothe radio bearer. In an example, MAC CE may indicate mapping restrictionfor the first logical channel and the second logical channel. As anexample of mapping restriction, the first logical channel may be mappedto one or more first cells/carriers and the second logical channel maybe mapped to one or more second cells/carriers. In an example, the oneor more first cells/carriers and the one or more second cells/carriersmay be different. The wireless device may receive a MAC CE toactivate/start and/or deactivate/stop the PDCP duplication for the oneor more first radio bearers. In an example, the MAC CE may comprise atleast one activation/deactivation bit that activates/starts and/ordeactivates/stops PDCP duplication for the one or more first radiobearers. In an example, the MAC CE may comprise a singleactivation/deactivation bit that activates/starts and/ordeactivates/stops PDCP duplication for the one or more first radiobearers. In an example, MAC CE may not comprise a payload (e.g., maycomprise zero bits). The presence of a MAC PDU subheader with LCIDcorresponding to the PDCP duplication control MAC CE may indicate thatPDCP duplication for the one or more first radio bearers areactivated/started. In an example, the MAC CE may comprise a field thatindicates the mapping restrictions for the logical channelscorresponding to the one or more first radio bearers. In an example, thefield may comprise one or more cell IDs corresponding to a logicalchannel corresponding to a bearer in the one or more first radiobearers. In an example, the wireless device may receive a downlinkcontrol information (DCI), e.g., in a PDCCH. The DCI may comprise anuplink grant for the wireless device. The uplink grant may indicatetransmission parameters for one or more transport blocks (TBs). Thetransmission parameters may comprise uplink resources for transmissionof the one or more TBs, power control command, MIMO parameters, HARQparameters, etc. In an example, the MAC entity may construct the one ormore TBs. The multiplexing and assembling entity may perform a logicalchannel prioritization procedure and multiplex MAC SDUs and/or MAC CEs.The wireless device may transmit the one or more TBs using the uplinkresources indicated by the uplink grant.

In an example embodiment, a wireless device may receive one or moremessages comprising configuration parameters for a plurality of cells.In an example, the one or more messages may comprise one or more RRCmessages. In an example, the configuration parameters may compriseparameters for one or more logical channels. In an example, theconfiguration parameters may comprise parameters for one or more radiobearers. In an example, the configuration parameters may indicatewhether PDCP duplication is configured for one or more first radiobearers. In an example, RRC may configure PDCP duplication for the oneor more first radio bearers. MAC CE may activate/start and/ordeactivate/stop the PDCP duplication for one or more second radiobearers of the one or more first radio bearers. The one or more secondradio bearers may be a subset of the one or more first radio bearers.The RRC configuration may comprise some of the PDCP duplicationparameters for the one or more first radio bearers. The MAC CE maycomprise some of the PDCP duplication parameters for the one or morefirst radio bearers and/or the one or more second radio bearers. In anexample, a radio bearer in the one or more first radio bearers may bemapped to a first logical channel and a second logical channel. In anexample, the one or more messages and/or the one or more RRC messagesmay indicate the first logical channel and the second logical channel.In an example, the MAC CE may indicate the first logical channel and thesecond logical channel. In an example, the MAC CE may comprise a fieldcomprising a first logical channel ID and a second logical channel ID.The buffers associated with the first logical channel may comprise datacorresponding to PDCP PDUs corresponding to the radio bearer. Thebuffers associated with the second logical channel may comprise datacorresponding to duplicate PDCP PDUs corresponding to the radio bearer.In an example, MAC CE may indicate mapping restriction for the firstlogical channel and the second logical channel. As an example of mappingrestriction, the first logical channel may be mapped to one or morefirst cells/carriers and the second logical channel may be mapped to oneor more second cells/carriers. In an example, the one or more firstcells/carriers and the one or more second cells/carriers may bedifferent. The wireless device may receive a MAC CE to activate/startand/or deactivate/stop the PDCP duplication for the one or more secondradio bearers. In an example, the MAC CE may comprise a field thatactivates/starts and/or deactivates/stops PDCP duplication for the oneor more second radio bearers. In an example, the field may comprise abitmap indicating the one or more second radio bearers in the one ormore first radio bearers. In an example, the MAC CE may comprise IDscorresponding to the one or more second radio bearers indicating PDCPduplication for the one or more second radio bearers areactivated/started and/or deactivated/stopped. In an example, the PDCPduplication control MAC CE may comprise a first format (e.g., comprisingone octet) or a second format (e.g., comprising a plurality of octetse.g., 2, 3, 4, octets, etc.). The format of the PDCP duplication MAC CEthat is used by the base station may depend on the number of radiobearers that are configured (e.g., with RRC) for PDCP duplication (e.g.,the number of the one or more first radio bearers). In an example, thePDCP duplication control MAC CE may comprise of one format (e.g., thefirst format). In an example, the MAC CE may comprise a field thatindicates the mapping restrictions for the logical channelscorresponding to the one or more first radio bearers. In an example, thefield may comprise one or more cell IDs corresponding to a logicalchannel corresponding to a bearer in the one or more first radiobearers. In an example, the wireless device may receive a downlinkcontrol information (DCI), e.g., in a PDCCH. The DCI may comprise anuplink grant for the wireless device. The uplink grant may indicatetransmission parameters for one or more transport blocks (TBs). Thetransmission parameters may comprise uplink resources for transmissionof the one or more TBs, power control command, MIMO parameters, HARQparameters, etc. In an example, the MAC entity may construct the one ormore TBs. The multiplexing and assembling entity may perform a logicalchannel prioritization procedure and multiplex MAC SDUs and/or MAC CEs.The wireless device may transmit the one or more TBs using the uplinkresources indicated by the uplink grant.

In an example embodiment, a MAC CE format as shown in FIG. 17 may beused. The MAC CE may comprise an octet indicating a bitmap may be usedthat may indicate the radio bearers to be activated/deactivated for PDCPduplication. A bit equal to one may indicate that the correspondingradio bearer is activated for PDCP duplication. A bit equal to zero mayindicate that the corresponding radio bearer is deactivated for PDCPduplication. In an example, the radio bearers may be sorted according totheir bearer IDs. In an example, B1 may correspond to the largest bearerID, B2 may correspond to the second largest bearer ID, and so on. In anexample, B1 may correspond to the smallest bearer ID, B2 may correspondto the second smallest bearer ID, and so on. Other criteria for sortingradio bearer IDs may be used. In an example, a single PDCP duplicationMAC CE format may be used (e.g., the first format or the second format).

In an example embodiment, a MAC CE format as shown in FIG. 18 may beused. The MAC CE may comprise two octets indicating a bitmap may be usedthat may indicate the radio bearers to be activated/deactivated for PDCPduplication. A bit equal to one may indicate that the correspondingradio bearer is activated for PDCP duplication. A bit equal to zero mayindicate that the corresponding radio bearer is deactivated for PDCPduplication. In an example, the radio bearers may be sorted according totheir bearer IDs. In an example, B1 may correspond to the largest bearerID, B2 may correspond to the second largest bearer ID, and so on. In anexample, B1 may correspond to the smallest bearer ID, B2 may correspondto the second smallest bearer ID, and so on. Other criteria for sortingradio bearer IDs may be used. In an example, a single PDCP duplicationMAC CE format may be used (e.g., the first format or the second format).

In an example, a MAC CE format according to FIG. 17 or FIG. 18 may beused depending on the number of bearers configured for PDCP duplicationand/or the number of bearers for which PDCP duplication isactivated/deactivated. In an example first format, an octet indicating abitmap may be used that may indicate the radio bearers to beactivated/deactivated for PDCP duplication. In an example, the basestation may use a first format MAC CE for PDCP duplication control inresponse to number of configured radio bearers for PDCP duplicationand/or the number of bearers activated/deactivated for PDCP duplicationbeing less than or equal to 8. In an example, the base station may use asecond format MAC CE for PDCP duplication control in response to numberof configured radio bearers for PDCP duplication and/or the number ofbearers activated/deactivated for PDCP duplication being larger than 8.In example, the second format MAC CE may comprise two octets. Otherexamples (e.g., three, four octets, etc.) may be used.

Example MAC CE formats for PDCP duplication control are shown in FIG. 17and FIG. 18. In an example, a plurality of MAC CE formats may be usedfor PDCP duplication control. In an example, the base station may use aformat in the plurality of formats depending on the number of bearersconfigured for PDCP duplication and/or the number of bearers for whichPDCP duplication is activated/deactivated. In an example first format,an octet indicating a bitmap may be used that may indicate the radiobearers to be activated/deactivated for PDCP duplication. In an example,the base station may use a first format MAC CE for PDCP duplicationcontrol in response to number of configured radio bearers for PDCPduplication and/or the number of bearers activated/deactivated for PDCPduplication being less than or equal to 8. In an example, the basestation may use a second format MAC CE for PDCP duplication control inresponse to number of configured radio bearers for PDCP duplicationand/or the number of bearers activated/deactivated for PDCP duplicationbeing larger than 8. In example, the second format MAC CE may comprisetwo octets. Other examples (e.g., three, four octets, etc.) may be used.A bit equal to one may indicate that the corresponding radio bearer isactivated for PDCP duplication. A bit equal to zero may indicate thatthe corresponding radio bearer is deactivated for PDCP duplication. Inan example, the radio bearers may be sorted according to their bearerIDs. In an example, B1 may correspond to the largest bearer ID, B2 maycorrespond to the second largest bearer ID, and so on. In an example, B1may correspond to the smallest bearer ID, B2 may correspond to thesecond smallest bearer ID, and so on. Other criteria for sorting radiobearer IDs may be used. In an example, a single PDCP duplication MAC CEformat may be used (e.g., the first format or the second format).

PDCP duplication is a method for improving packet transmissionreliability in a wireless network. The base station may configure PDCPduplication for one or more bearers of a wireless device and maydynamically activate or deactivate the PDCP duplication with a controlelement (e.g., MAC control element). A wireless device may be configuredwith up to 32 bearers and each bearer may be associated with a beareridentifier. Implementation of existing MAC CE mechanisms will result inincreased downlink signaling overhead for PDCP duplication activation.

For example, if the control element for PDCP duplication controlincludes the bearer identifiers for which the PDCP duplication isactivated or deactivated, the size of the MAC CE may require largenumber of bits. For example, if eight bearers are configured with PDCPduplication and a bearer identifier includes five bit, forty bits (fiveoctets) will be needed to indicate the bearer identifiers for the eightbearers configured with PDCP duplication. This increases downlinksignaling overhead and leads to inefficient resource utilization. Thereis a need to efficiently indicate the status of PDCP duplication (e.g.,activation or deactivation) for bearers configured with PDCPduplication.

For example, if the control element for PDCP duplication controlincludes a bitmap for which the PDCP duplication is activated ordeactivated for configured bears, the size of the MAC CE may require 32bits. For example, 32 (four octets) may be needed to indicateduplication activation/deactivation for each bearer identifier from 0 to31. In another example, when less than 32 bearers are configured, thebitmap may includes bits for configured bearer identifiers, for example,18 bits for 18 configured bearers. This increases downlink signalingoverhead and leads to inefficient resource utilization. There is a needto efficiently indicate the status of PDCP duplication (e.g., activationor deactivation) for bearers configured with PDCP duplication.

Example embodiments provide efficient control element formats (e.g. MACCE formats) and PDCP duplication processes to activate/deactivate PDCPduplication bearers configured with PDCP duplication. Exampleembodiments reduces downlink signaling overhead and leads to efficientresource utilization compared with when legacy MAC CE mechanisms areimplemented.

An example PDCP duplication procedure and PDCP duplication MAC CE formatis shown in FIG. 23. In an example, a wireless device may receive one ormore messages comprising configuration parameters for a wireless device.In an example, the configuration parameters may comprise bearconfigurations parameters for a plurality of bearers. For example, theconfiguration parameters may comprise one or more bearer identifiers forone or more bearers. In an example, the plurality of bearers maycomprise data radio bearers and signaling radio bearers. In an example,a bearer in the plurality of bearers may be identified with a beareridentifier. In an example, the configuration parameters may indicatethat one or more first bearers in the plurality of bearers areconfigured with PDCP duplication. The configuration parameters maycomprise PDCP duplication configuration parameters for the one or morefirst bearers. In an example, a bearer in the one or more first bearersmay be data radio bearers. In an example, the one or more first bearersmay be data radio bearers.

The wireless device may receive a control element. In an example, thecontrol element may be a MAC control element. In an example, the controlelement may be multiplex with downlink data in a downlinkpacket/transport block. A subheader corresponding to the control elementmay comprise a logical channel identifier indicating that the controlelement is a PDCP duplication control control element, e.g., foractivation or deactivation of PDCP duplication for one or more bearers.

In an example, the control element may comprise a sequence of activationbits. In an example, the sequence of activation bits may be foractivation and/or deactivation of PDCP duplication for the one or morefirst bearers. In an example, the sequence of activation bits maycomprise a first bit for a first bearer in the one or more firstbearers. The packet duplication MAC CE does not include beareridentifiers. Example embodiments reduce downlink signaling overhead andleads to efficient resource utilization by implementing one bit foractivation/deactivation control element.

In an example, the first bit may have a first position in the oneoctet/sequence of activation bits/control element. The first position ofthe first bit may identify a second position of first bearer identifierin an ordered list of bearer identifiers of the one or more firstbearers configured with PDCP duplication. In an example, at least onemessage (e.g. RRC message) may configure 16 bearers and configure 6 ofthe 16 bearers with packet duplication and the 10 other bearers with nopacket duplication. Example embodiments implement an ordered list ofbearer identifiers of 6 bearer that are configured with PDCP duplication(e.g. see FIG. 23). This further reduces the size of the MAC CE andreduces downlink signaling overhead and increases spectral efficiency.Ordering the bearer identifiers of bearers configured with PDCPduplication, enables an efficient mechanism to determine the position ofan activation bit corresponding to a first bearer configured with PDCPduplication and reduces the size of the MAC CE.

In an example, the ordered list of the bearer identifiers of the one ormore first bearers may be an ascending ordered list of the beareridentifiers of the one or more first bearers. In an example, a firstposition of the first bit in the one octet/sequence of activationbits/control element may be same as the second position of the firstbearer in the one or more first bearers. In an example, a first value ofthe first bit may indicate whether the PDCP duplication for the firstbearer is activated or deactivated. In an example, the PDCP duplicationfor the first bearer may be activated in response to the first value ofthe first bit being one. In an example, the PDCP duplication for thefirst bearer may be deactivated in response to the first value of thefirst bit being zero. Example embodiments reduces the size of the MAC CEto only one octet including 8 bits. In an example, the control elementmay have a fixed size. In an example, the control element may have afixed size of one octet. Example embodiments enables using a fixed sizeMAC CE which further reduces the MAC CE subheader size, because a fixedsize MAC CE does not require a length field. This further reducesdownlink signaling overhead and increases spectral efficiency. Exampleembodiments limits the number of bearers configured with PDCPduplication to 8 to enable implementation of a fixed one octet size forMAC CE. This limitation further increases downlink signaling overhead byenabling implementation of a fixed MAC CE that has a smaller subheadersize.

In an example, the wireless device may receive a first uplink grant fora first cell and a second uplink grant for a second cell. In an example,in response to the control element indicating that the PDCP duplicationis activated for the first bearer, the wireless device may transmit afirst packet corresponding to the first bearer via the first cell and aduplicate of the first packet via the second cell. The one or moremessages may comprise configuration parameters for the first cell andthe second cell. In an example, a first RLC entity may handle packetsfrom the first radio bearer. The wireless device may add a second RLCentity to handle duplicate packets corresponding to the first radiobearer. In an example, the first packet may correspond to the first RLCentity and the second packet may correspond to the second RLC entity. Inan example, a first buffer associated with a first logical channel maycomprise the first packet corresponding to the first radio bearers and asecond buffer associated with a second logical channel may comprise theduplicate of the first packet. In an example, configuration parametersfor the first logical channel may indicate that the first cell is afirst allowed serving cell for transmission of data from the firstlogical channel. In an example, configuration parameters for the secondlogical channel may indicate that the second cell is a second allowedserving cell for transmission of data from the second logical channel.

In an example, in response to PDCP duplication being deactivated for thefirst bearer, the wireless device may no longer apply the logicalchannel restriction for the first logical channel. The wireless devicemay multiplex data from the first logical channel in a transport blockthat is transmitted via the second cell in response to the PDCPduplication being deactivate for the first bearer. In an example, thewireless device may receive a control element indicating that the PDCPduplication is deactivated for the first bear. The wireless device mayno longer apply the logical channel restriction for the first logicalchannel and may transmit the first logical channel via the first cell orthe second cell in response to the PDCP duplication being deactivatedfor the first bearer.

Example PDCP duplication control MAC CE formats are shown in FIG. 19. Inan example, the MAC CE may comprise IDs corresponding to the one or moresecond radio bearers. The one or more second radio bearers may be asubset of one or more first radio bearers configured for PDCPduplication, e.g., by RRC. In an example, in FIG. 19(a), the radiobearers whose IDs are included in the MAC may be activated for PDCPduplication. The radio bearers that are configured for PDCP duplication(e.g., by RRC) and their IDs are not included in the MAC CE may bedeactivated for PDCP duplication. In the example, in FIG. 19(b), anactivation/deactivation field may correspond to a radio bearer ID. Theactivation/deactivation field may comprise one or more bits. The valueof the one or more bits may indicate if the corresponding radio beareris activated for PDCP duplication or PDCP duplication for thecorresponding radio bearer is deactivated/stopped. For example, a valueof one may indicate that PDCP duplication is activated for thecorresponding radio bearer and a value of zero may indicate that thePDCP duplication for the corresponding radio bearers isdeactivated/stopped. In an example, for the MAC CE format in FIG. 19(b),n (e.g., the number of radio bearer IDs in the MAC CE) may equal thenumber of bearers configured for PDCP duplication (e.g., by RRC).

An example PDCP duplication control MAC CE format is shown in FIG. 20.The MAC CE may comprise a first field indicating one or more secondradio bearers that are activated for PDCP duplication for the wirelessdevice. The one or more second radio bearers may be a subset of one ormore first radio bearers configured for PDCP duplication for thewireless device (e.g., by RRC). In an example shown in FIG. 20, thefirst field may comprise one octet. Larger sizes of the first field(e.g., larger number of octets) may be used for the first field if thenumber of radio bearers configured and/or activated for PDCP duplicationis larger (e.g., larger than 8). In an example, the MAC CE for PDCPduplication control may comprise a second plurality of fields. Thenumber of the second plurality of fields may be equal to or larger thanthe number of activated and/or configured radio bearers for PDCPduplication and/or other numbers. In an example, for a radio bearerindicated to be deactivated/stopped for PDCP duplication, there may notbe a corresponding field in the second plurality of fields. One or morefields in the plurality of fields may correspond to a radio bearer(e.g., indicated to be activated for PDCP duplication) in the firstfield. In an example, a field in the one or more fields in the pluralityof fields corresponding to a first radio bearer in the first field(e.g., indicated to be activated for PDCP duplication) may indicate oneor more first cells/carriers and one or more second cells/carriers. Theone or more first cells/carriers may be used for mapping a first logicalchannel corresponding to the first radio bearer and the one or moresecond logical channel may be used for mapping a second logical channel(e.g., duplicate logical channel) corresponding to the first radiobearer. In an example, buffers associated to the first logical channelmay comprise data corresponding to PDCP PDUs corresponding to the firstradio bearer. In an example, the buffers associated to the secondlogical corresponding to the first radio bearer may comprise datacorresponding to duplicate PDCP PDUs corresponding to the first radiobearer. In an example, a field in the one or more fields in theplurality of fields corresponding to a first radio bearer in the firstfield (e.g., indicated to be activated for PDCP duplication) mayindicate other parameters related to PDCP duplication for the firstradio bearer (e.g., the first logical channel, the second logicalchannel, etc.).

An example PDCP duplication control MAC CE format is shown in FIG. 21.In an example, the MAC CE may comprise a first plurality of fieldscomprising IDs corresponding to one or more second radio bearers. Theone or more second radio bearers may be a subset of one or more firstradio bearers configured for PDCP duplication, e.g., by RRC. The radiobearers whose IDs are included in the MAC CE may be activated for PDCPduplication. The radio bearers that are configured for PDCP duplication(e.g., by RRC) and their IDs are not included in the MAC CE may bedeactivated for PDCP duplication. The MAC CE may comprise a secondplurality of fields. One or more fields in the second plurality offields may correspond to radio bearer ID. A field in the one or morefields corresponding to the radio bearer ID may indicate one or morefirst cells/carriers and one or more second cells/carriers. The one ormore first cells/carriers may be used for mapping a first logicalchannel corresponding to the radio bearer and the one or more secondlogical channel may be used for mapping a second logical channel (e.g.,duplicate logical channel) corresponding to the radio bearer. In anexample, buffers associated to the first logical channel may comprisedata corresponding to PDCP PDUs corresponding to the radio bearer. In anexample, the buffers associated to the second logical corresponding tothe radio bearer may comprise data corresponding to duplicate PDCP PDUscorresponding to the radio bearer. In an example, a field in the one ormore fields in the plurality of fields corresponding to the radio bearermay indicate other parameters related to PDCP duplication for the radiobearer (e.g., the first logical channel, the second logical channel,etc.).

An example PDCP duplication control MAC CE format is shown in FIG. 22.The MAC CE may comprise a first plurality of fields comprising radiobearer IDs for a plurality of radio bearers. In an example, the numberof the first plurality of fields may be equal to the number of radiobearers configured for PDCP duplication (e.g., by RRC). In an example,the MAC CE may comprise a second plurality of fields. A field in thesecond plurality of fields may indicate whether PDCP duplication isactivated/started and/or deactivated/stopped for a radio bearercorresponding to the field. In an example, the MAC CE may comprise athird plurality of fields. In an example, a radio bearer ID maycorrespond to one or more fields in the third plurality of fields. In anexample, a radio bearer ID whose corresponding radio bearer is activatedfor PDCP duplication (e.g., as indicated by a corresponding field in thesecond plurality of fields) may correspond to one or more fields in thethird plurality of fields. In an example, a radio bearer ID whosecorresponding radio bearer is deactivated/stopped for PDCP duplication(e.g., as indicated by a corresponding field in the second plurality offields) may not correspond to a field in the third plurality of fields.In an example, a field in the one or more fields may indicate one ormore first cells/carriers and one or more second cells/carriers. The oneor more first cells/carriers may be used for mapping a first logicalchannel corresponding to the radio bearer and the one or more secondlogical channel may be used for mapping a second logical channel (e.g.,duplicate logical channel) corresponding to the radio bearer. In anexample, buffers associated to the first logical channel may comprisedata corresponding to PDCP PDUs corresponding to the radio bearer. In anexample, the buffers associated to the second logical corresponding tothe radio bearer may comprise data corresponding to duplicate PDCP PDUscorresponding to the radio bearer. In an example, a field in the one ormore fields in the third plurality of fields corresponding to the radiobearer may indicate other parameters related to PDCP duplication for theradio bearer (e.g., the first logical channel, the second logicalchannel, etc.).

In an example embodiment, a wireless device may receive one or moremessages comprising configuration parameters for a plurality of cells.In an example, the one or more messages may comprise one or more RRCmessages. In an example, the configuration parameters may compriseparameters for one or more logical channels. In an example, theconfiguration parameters may comprise parameters for one or more radiobearers. In an example, the configuration parameters may indicatewhether PDCP duplication is configured for one or more first radiobearers. In an example, the base station may activate/start and/ordeactivate/stop PDCP duplication for one or more second radio bearers inthe one or more first radio bearers. The base station may activate/startand/or deactivate/stop PDCP duplication for the one or more second radiobearers in the one or more first radio bearers using a PDCP duplicationcontrol MAC CE. In an example, a plurality of sets of semi-persistentscheduling (SPS) grants and/or grant-free resources may be configured inresponse to PDCP duplication being configured and/or activated/startedfor a radio bearer in a wireless device. In an example, a first set ofSPS grants and/or grant-free resources may be configured fortransmission of data in a first logical channel corresponding to a radiobearer configured and/or activated for PDCP duplication. A second set ofSPS grants and/or grant-free resources may be configured fortransmission of data in a second logical channel corresponding to aradio bearer configured and/or activated for PDCP duplication. In anexample, the buffers associated with the first logical channel maycomprise data corresponding to PDCP PDUs corresponding to the radiobearer. The buffers associated with the second logical channel maycomprise data corresponding to duplicate PDCP PDUs corresponding to theradio bearer.

In an example embodiment, the wireless device may receive a PDCPduplication control MAC CE indicating PDCP duplication activation for afirst radio bearer. The reception of the PDCP duplication control MAC CEmay implicitly activate the first set of SPS grants and/or grant-freeresources, and/or may implicitly activate the second set of SPS grantsand/or grant-free resources. In an example, the uplink resources and/orsome other transmission parameters (e.g., HARQ parameters e.g., HARQ ID,MCS, etc.) for the first set of SPS grants and/or grant-free resourcesand/or the second set of SPS grants and/or grant-free resources may beconfigured by RRC and/or PDCCH and/or may be known by the wirelessdevice.

In an example embodiment, the PDCP duplication control MAC CE indicatingPDCP duplication activation for a first radio bearer may comprise one ormore fields indicating whether the first set of SPS grants and/orgrant-free resources, and/or the second set of SPS grants and/orgrant-free resources may be activated. The one or more fields indicatingwhether the first set of SPS grants and/or grant-free resources, and/orthe second set of SPS grants and/or grant-free resources may beactivated may be incorporated in the example MAC CE formats illustratedin FIG. 17-FIG. 23. In an example, the uplink resources and/or othertransmission parameters (e.g., HARQ parameters, etc.) for the first setof SPS grants and/or grant-free resources and/or the second set of SPSgrants and/or grant-free resources may be configured by RRC and/or maybe known by the wireless device. In an example, a first portion oftransmission parameters for the first set of SPS grants and/orgrant-free resources and/or the second set of SPS grants and/orgrant-free resources may be configured by RRC and a second portion oftransmission parameters for the first set of SPS grants and/orgrant-free resources and/or the second set of SPS grants and/orgrant-free resources may be indicated by the PDCP duplication controlMAC CE and/or may be known by the wireless device. In an example,transmission parameters for the first set of SPS grants and/orgrant-free resources and/or the second set of SPS grants and/orgrant-free resources may be indicated to the wireless device.

In an example embodiment, the wireless device may be configured with afirst set of SPS grants and/or grant-free resources for a first logicalchannel corresponding to a first radio bearer configured and/oractivated with PDCP duplication and/or a second set of SPS grants and/orgrant-free resources for a second logical channel (e.g., duplicatelogical channel) corresponding to the first radio bearer. The wirelessdevice may receive a PDCP duplication control MAC CE indicating PDCPduplication deactivation/stopping for the first radio bearer. In anexample, the reception of PDCP duplication control MAC CE indicatingstopping and/or deactivating PDCP duplication for the first radio bearermay implicitly release the first set of SPS grants and/or grant-freeresources, and/or may implicitly release the second set of SPS grantsand/or grant-free resources.

In an example embodiment, the wireless device may be configured with afirst set of SPS grants and/or grant-free resources for a first logicalchannel corresponding to a first radio bearer configured and/oractivated with PDCP duplication and/or a second set of SPS grants and/orgrant-free resources for a second logical channel (e.g., duplicatelogical channel) corresponding to the first radio bearer. The wirelessdevice may receive a PDCP duplication control MAC CE indicating PDCPduplication deactivation/stopping for the first radio bearer. In anexample, the PDCP duplication control MAC CE may comprise one or morefields indicating whether the first set of SPS grants and/or grant-freeresources, and/or the second set of SPS grants and/or grant-freeresources may be released. The one or more fields indicating whether thefirst set of SPS grants and/or grant-free resources, and/or the secondset of SPS grants and/or grant-free resources may be released may beincorporated in the example MAC CE formats illustrated in FIG. 17-FIG.23.

In an example embodiment, the wireless device may be configured with afirst set of SPS grants and/or grant-free resources for a first logicalchannel corresponding to a first radio bearer configured and/oractivated with PDCP duplication and/or a second set of SPS grants and/orgrant-free resources for a second logical channel (e.g., duplicatelogical channel) corresponding to the first radio bearer. In an example,if buffer associated with the first logical channel is emptied, thewireless device may flush the buffers associated with the second logicalchannel. The wireless device may not use the grants for the secondlogical channel until data arrives in the first and second logicalchannel. The wireless device may use the grants for logical channelsother than the first logical channel and the second logical in themeantime if needed, e.g., in response to the first logical channel andthe second logical channel being empty and/or in response to data notarriving for the first logical channel and the second logical channel,until data arrives in the first logical channel and the second logicalchannel.

In an example embodiment, the wireless device may be configured with afirst set of SPS grants and/or grant-free resources for a first logicalchannel corresponding to a first radio bearer configured and/oractivated with PDCP duplication and/or a second set of SPS grants and/orgrant-free resources for a second logical channel (e.g., duplicatelogical channel) corresponding to the first radio bearer. In an example,the configuration parameters for the second set of SPS grants and/orgrant-free resources may be derived implicitly from the configurationparameters of the first set of SPS grants and/or grant-free resources.In an example, the base station may activate the first set of SPS grantsand/or grant-free resources and the second set of SPS grants and/orgrant-free resources using a first SPS activation PDCCH. In an example,the base station may activate simultaneously the first set of SPS grantsand/or grant-free resources and the second set of SPS grants and/orgrant-free resources using a first SPS activation PDCCH. In an example,the base station may release/deactivate the first set of SPS grantsand/or grant-free resources and the second set of SPS grants and/orgrant-free resources using a first SPS release/deactivation PDCCH. In anexample, the base station may release/deactivate simultaneously thefirst set of SPS grants and/or grant-free resources and the second setof SPS grants and/or grant-free resources using a first SPSrelease/deactivation PDCCH. In an example, the SPS activation and/or theSPS release/deactivation PDCCH may comprise a bit-map indicating forwhich of the first logical channel and/or the second logical channel theset of SPS grants and/or grant-free resources may be activated and/orreleased.

In an example embodiment, the wireless device may be configured with afirst set of SPS grants and/or grant-free resources for a first logicalchannel corresponding to a first radio bearer configured and/oractivated with PDCP duplication and/or a second set of SPS grants and/orgrant-free resources for a second logical channel (e.g., duplicatelogical channel) corresponding to the first radio bearer. In an example,the configuration parameters for the second set of SPS grants and/orgrant-free resources may be derived implicitly from the configurationparameters of the first set of SPS grants and/or grant-free resources.In an example, the transmission parameters (e.g., uplink resources, HARQID, grant TTI, periodicity, MCS, etc.) for the second set of SPS grantsand/or grant-free resources may be implicitly derived from thetransmission parameters corresponding to the first set of SPS grantsand/or grant-free resources. In an example, the starting TTI for thesecond set of SPS grants and/or grant-free resources may be a shift tothe first set of SPS grants and/or grant-free resources. In an example,the shift may be indicated to the wireless device (e.g., using RRCand/or MAC CE and/or PDCCH). In an example, periodicity of the secondset of SPS grants and/or grant-free resources may be same as periodicityof the first set of SPS grants and/or grant-free resources. In anexample, HARQ ID for a second SPS grant and/or grant free resource inthe second set of SPS grants and/or grant-free resources may be a shiftto a first SPS grant and/or grant-free resource. In an example, theshift may be indicated to the wireless device e.g., using RRC and/or MACCE and/or PDCCH).

A packet corresponding to a radio bearer configured with PDCPduplication and its corresponding duplicate packet are transmitted viadifferent carriers. Periodic resource allocation may be used to transmitpackets corresponding to a radio bearer configured with PDCPduplication. Using legacy procedures, the wireless device needs toreceive two separate activation DCI for two periodic resource allocationactivations on two different cells. The legacy procedures increasedownlink control signaling. There is a need to enhance the efficiency ofdownlink control signaling for activation of periodic resourceallocation when used for transmission of packets from bearers configuredwith PDCP duplication. Example embodiments enhance the downlink controlsignaling efficiency for activation of periodic resource allocation whenused for transmission of packets of bearers configured with PDCPduplication.

An example embodiment is shown in FIG. 24. In an example, a wirelessdevice may receive one or more messages comprising configurationparameters. In an example, the one or more messages may comprise RRCmessages. The one or more messages may comprise first configurationparameters for a first periodic resource allocation and a secondperiodic resource allocation. The first periodic resource allocation maycomprise a first periodicity and one or more first parameters fordetermining resources associated with the first periodic resourceallocation. The first periodic resource allocation may comprise a secondperiodicity and one or more second parameters for determining resourcesassociated with the second periodic resource allocation. The one or moremessages may comprise second configuration parameters for PDCP packetduplication of a first bearer in a plurality of bearers. In an example,the one or more messages may comprise configuration parameters for theplurality of bearers. The wireless device may receive a control element.In an example, the control element may be a MAC control element. In anexample, the control element may indicate activation of the PDCPduplication for the first bearer.

The wireless device may receive a DCI indicating activation of the firstperiodic resource allocation. In an example, the configurationparameters for the first periodic resource allocation may comprise afirst radio network temporary identifier. The DCI may be associated withthe first radio network temporary identifier. In an example, thewireless device may validate the DCI as an activating DCI for the firstperiodic resource allocation. In response to receiving the DCI, thewireless device may activate a first plurality of resourcescorresponding to the first periodic resource allocation on a first celland a second plurality of resources corresponding to the second periodicresource allocation on a second cell. In an example, the wireless devicemay transmit first data packets of the first radio bearer via the firstplurality of resources on the first cell. The wireless device maytransmit duplicate of first data packets via the second plurality ofresources of the second cell.

According to various embodiments, a device such as, for example, awireless device, off-network wireless device, a base station, and/or thelike, may comprise one or more processors and memory. The memory maystore instructions that, when executed by the one or more processors,cause the device to perform a series of actions. Embodiments of exampleactions are illustrated in the accompanying figures and specification.Features from various embodiments may be combined to create yet furtherembodiments.

FIG. 27 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 2710, a wireless device may receive one ormore messages comprising configuration parameters indicating that one ormore first bearers in a plurality of bearers are configured with packetdata convergence protocol (PDCP) duplication. Each bearer in theplurality of bearers may be identified by a bearer identifier. At 2720,a control element of a fixed size of one octet may be received. Thecontrol element may comprise a sequence of activation bits comprising afirst activation bit for a first bearer in the one or more firstbearers. A first position of the first activation bit in the one octetmay identify a second position of a first bearer identifier in anordered list of bearer identifiers of the one or more first bearersconfigured with the PDCP duplication. A first value of the firstactivation bit may indicate whether the PDCP duplication for the firstbearer is activated or deactivated. At 2730, a first packet may betransmitted in response to the control element indicating that the PDCPduplication is activated for the first bearer. The first packet maycorrespond to the first bearer via a first cell and a duplicate of thefirst packet via a second cell.

According to an embodiment, a first buffer associated with a firstlogical channel may comprise the first packet; and a second bufferassociated with a second logical channel may comprise the duplicate ofthe first packet. According to an embodiment, the one or messages mayindicate that: the first cell is a first allowed serving cell fortransmission of data from the first logical channel; and the second cellis a second allowed serving cell for transmission of data from thesecond logical channel. According to an embodiment, the one or messagesmay indicate that: a first plurality of cells are first allowed servingcells for transmission of data from the first logical channel. The firstplurality of cells may comprise the first cell. According to anembodiment, a second plurality of cells may be second allowed servingcells for transmission of data from the second logical channel. Thesecond plurality of cells may comprise the second cell.

According to an embodiment, the first packet may correspond to a firstradio link control (RLC) entity and a first logical channel; and theduplicate of the first packet may correspond to a second RLC entity anda second logical channel. According to an embodiment, a first uplinkgrant for transmission of the first packet may be received via the firstcell; and a second uplink grant for transmission of the duplicate of thefirst packet may be received via the second cell.

According to an embodiment, the ordered list may be an ascending orderedlist. According to an embodiment, the ordered list may be a descendingordered list. According to an embodiment, the first position may be sameas the second position. According to an embodiment, the control elementmay indicate: activation of the PDCP duplication for the first bearer inresponse to the first value being one; and deactivation of the PDCPduplication for the first bearer in response to the first value beingzero. According to an embodiment, a bearer in the plurality of bearersmay be a data radio bearer. According to an embodiment, the controlelement may be associated with a logical channel identifier indicatingthat the control element is for PDCP duplication activation/deactivationof one or more bearers.

According to an embodiment, a second control element indicating that thePDCP duplication is deactivated for the first bearer may be received.According to an embodiment, an uplink grant for the second cell may bereceived. According to an embodiment, a packet associated with the firstbearer based on the uplink grant may be transmitted.

FIG. 28 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 2810, a wireless device may receiveconfiguration parameters indicating that one or more bearers areconfigured with packet data convergence protocol (PDCP) duplication. At2820, a control element of a fixed size of one octet may be received.The control element may comprise a sequence of activation bitscomprising a first activation bit for a first bearer of the one or morebearers. A first position of the first activation bit in the one octetmay identify a second position of a first bearer identifier in anordered list of bearer identifiers of the one or more bearers. A firstvalue of the first activation bit may indicate the PDCP duplication forthe first bearer is activated. At 2830, a first packet corresponding tothe first bearer and a duplicate of the first packet may be transmitted.According to an embodiment, each bearer in the one or more bearers maybe identified by a bearer identifier.

FIG. 29 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 2910, a control element comprisingduplication activation bits may be received. The duplication activationbits may comprise a first duplication activation bit for a first bearer.A first position of the first duplication activation bit in the controlelement may identify a second position of a first bearer identifier inan ordered list of bearer identifiers of one or more bearers configuredwith duplication. In response to the duplication being activated for thefirst bearer, a first packet and a duplicate of the first packet may betransmitted at 2920.

According to an embodiment, one or more messages may be received. Theone or more messages may comprise configuration parameters indicatingthat one or more bearers comprising the first bearer are configured withthe duplication. According to an embodiment, the duplication maycomprise packet data convergence protocol duplication. According to anembodiment, each bearer in the one or more bearers may be identified bya bearer identifier. According to an embodiment, a first value of thefirst duplication activation bit may indicate whether the duplicationfor the first bearer is activated or deactivated. According to anembodiment, the first packet may be transmitted via a first cell and theduplicate of the first packet may be transmitted via a second cell.

FIG. 30 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 3010, a base station may transmit one or moremessages. The one or more messages may comprise configuration parametersindicating that one or more first bearers in a plurality of bearers areconfigured with packet data convergence protocol (PDCP) duplication.Each bearer in the plurality of bearers may be identified by a beareridentifier. At 3020, a control element of a fixed size of one octet maybe transmitted. The control element may comprise a sequence ofactivation bits comprising a first activation bit for a first bearer inthe one or more first bearers. A first position of the first activationbit in the one octet may identify a second position of a first beareridentifier in an ordered list of bearer identifiers of the one or morefirst bearers configured with the PDCP duplication. A first value of thefirst activation bit may indicate whether the PDCP duplication for thefirst bearer is activated or deactivated. At 3030, in response to thecontrol element indicating that the PDCP duplication is activated forthe first bearer, a first packet corresponding to the first bearer maybe received via a first cell and a duplicate of the first packet may bereceived via a second cell.

According to an embodiment, a first buffer may be associated with afirst logical channel comprises the first packet. According to anembodiment, a second buffer may be associated with a second logicalchannel comprises the duplicate of the first packet. According to anembodiment, the one or messages may indicate that: the first cell is afirst allowed serving cell for transmission of data from the firstlogical channel; and the second cell is a second allowed serving cellfor transmission of data from the second logical channel. According toan embodiment, the one or messages may indicate that a first pluralityof cells are first allowed serving cells for transmission of data fromthe first logical channel. The first plurality of cells may comprise thefirst cell. According to an embodiment, the one or messages may indicatethat a second plurality of cells are second allowed serving cells fortransmission of data from the second logical channel. The secondplurality of cells may comprise the second cell.

According to an embodiment, the first packet may correspond to a firstradio link control (RLC) entity and a first logical channel; and theduplicate of the first packet may correspond to a second RLC entity anda second logical channel. According to an embodiment, a first uplinkgrant for transmission of the first packet may be transmitted via thefirst cell. According to an embodiment, a second uplink grant fortransmission of the duplicate of the first packet may be transmitted viathe second cell. According to an embodiment, the ordered list may be anascending ordered list. According to an embodiment, the ordered list maybe a descending ordered list. According to an embodiment, the firstposition may be same as the second position. According to an embodiment,the control element may indicate: activation of the PDCP duplication forthe first bearer in response to the first value being one; anddeactivation of the PDCP duplication for the first bearer in response tothe first value being zero.

According to an embodiment, a bearer in the plurality of bearers may bea data radio bearer. According to an embodiment, the control element maybe associated with a logical channel identifier indicating that thecontrol element is for PDCP duplication activation/deactivation of oneor more bearers. According to an embodiment, a second control elementindicating that the PDCP duplication is deactivated for the first bearermay be transmitted. According to an embodiment, an uplink grant for thesecond cell may be transmitted. According to an embodiment, a packetassociated with the first bearer based on the uplink grant may betransmitted.

FIG. 31 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 3110, a base station may transmitconfiguration parameters. The configuration parameters may indicate thatone or more bearers are configured with packet data convergence protocol(PDCP) duplication. At 3120, a control element of a fixed size of oneoctet may be transmitted. The control element may comprise a sequence ofactivation bits comprising a first activation bit for a first bearer ofthe one or more bearers. A first position of the first activation bit inthe one octet may identify a second position of a first beareridentifier in an ordered list of bearer identifiers of the one or morebearers. A first value of the first activation bit may indicate the PDCPduplication for the first bearer is activated. A first packet may bereceived at 3130. The first packet may correspond to the first bearerand a duplicate of the first packet. According to an embodiment, eachbearer in the one or more bearers may be identified by a beareridentifier.

FIG. 32 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. A control element may be transmitted at 3210.The control element may comprise duplication activation bits. Theduplication activation bits may comprise a first duplication activationbit for a first bearer. A first position of the first duplicationactivation bit in the control element may identify a second position ofa first bearer identifier in an ordered list of bearer identifiers ofone or more bearers configured with duplication. At 3220, a first packetand a duplicate of the first packet may be received in response to theduplication being activated for the first bearer.

According to an embodiment, one or more messages may be transmitted. Theone or more messages may comprise configuration parameters indicatingthat the one or more bearers comprising the first bearer are configuredwith duplication. According to an embodiment, the duplication maycomprise packet data convergence protocol duplication. According to anembodiment, each bearer in the one or more bearers may be identified bya bearer identifier. According to an embodiment, a first value of thefirst duplication activation bit may indicate whether the duplicationfor the first bearer is activated or deactivated. According to anembodiment, the first packet may be transmitted via a first cell and theduplicate of the first packet may be transmitted via a second cell.

FIG. 33 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 3310, a wireless device may receive one ormore messages. The one or more messages may comprise: a parameterindicating that uplink duplication may be configured for a bearercorresponding to a first logical channel and a second logical channel;first mapping restrictions of the first logical channel to at least onefirst cell; and second mapping restrictions of the second logicalchannel to at least one second cell. At 3320, a control elementindicating activation or deactivation of duplication for the bearer maybe received. If the control element indicates activation of theduplication (at 3330), the first mapping restrictions may be applied tothe first logical channel and the second mapping restrictions may beapplied to the second logical channel at 3340. If the control elementindicates deactivation of the duplication (at 3350), the first mappingrestrictions may be lifted from the first logical channel and the secondmapping restrictions may be lifted from the second logical channel at3360.

According to an embodiment, a first buffer associated with the firstlogical channel may comprise a first packet corresponding to the bearer;and a second buffer associated with the second logical channel maycomprise a duplicate of the first packet. According to an embodiment,the first logical channel may correspond to a first radio link control(RLC) entity; and the second logical channel may correspond to a secondRLC entity.

According to an embodiment, the one or messages may comprise firstconfiguration parameters of the first logical channel and secondconfiguration parameters of the second logical channel. According to anembodiment, the first configuration parameters may indicate the firstmapping restrictions. According to an embodiment, the secondconfiguration parameters may indicate the second mapping restrictions.

According to an embodiment, first data of the first logical channel maybe transmitted via the at least one second cell when the first mappingrestrictions are lifted. According to an embodiment, first data of thefirst logical channel may be transmitted via at least one of the atleast one first cell or the at least one second cell when the firstmapping restrictions are lifted.

According to an embodiment, first data of the first logical channel maybe transmitted via the at least one first cell in response to applyingthe first mapping restrictions; and second data of the second logicalchannel may be transmitted via the at least one second cell in responseto applying the second mapping restrictions. According to an embodiment,the duplication may comprise packet data convergence protocolduplication. According to an embodiment, the bearer may be a data radiobearer. According to an embodiment, a logical channel prioritizationprocedure may be applied based on the first mapping restriction and thesecond mapping restriction.

FIG. 34 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 3410, a wireless device may receive one ormore messages. The one or more messages may comprise: a parameterindicating that duplication may configured for a bearer corresponding toa first logical channel and a second logical channel; first mappingrestrictions of the first logical channel to at least one first cell;and second mapping restrictions of the second logical channel to atleast one second cell. At 3420, a control element indicatingdeactivation of the duplication for the bearer may be received. At 3430,in response to deactivation of the duplication, the first mappingrestrictions and the second mapping restrictions may be lifted.According to an embodiment, first data of the first logical channel maybe transmitted via the at least one second cell when the first mappingrestrictions are lifted. According to an embodiment, first data of thefirst logical channel may be transmitted via at least one of the atleast one first cell or the at least one second cell when the firstmapping restrictions are lifted.

FIG. 35 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 3510, a wireless device may receiveconfiguration parameters for a first periodic resource allocation and asecond periodic resource allocation. At 3520, a control elementindicating activation of duplication for a bearer may be received. At3530, a downlink control information (DCI) may be received. At 3540, afirst plurality of resources may be activated in response to receivingthe DCI. The first plurality of resources may correspond to the firstperiodic resource allocation on a first cell and a second plurality ofresources corresponding to the second periodic resource allocation on asecond cell. First packets of the bearer may be transmitted via thefirst plurality of resources. A duplicate of the first packets may betransmitted via the second plurality of resources.

According to an embodiment, the duplication may be packet dataconvergence protocol duplication. According to an embodiment, the bearermay be a data radio bearer. According to an embodiment, the bearer maycorrespond to a first logical channel and a second logical channel.According to an embodiment, a first buffer associated with the firstlogical channel may comprise the first packets; and a second bufferassociated with the second logical channel may comprise the duplicate ofthe first packets. According to an embodiment, the control element maybe a medium access control (MAC) control element.

FIG. 36 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 3610, a wireless device may receiveconfiguration parameters for a first periodic resource allocation and asecond periodic resource allocation. At 3620, a control element may bereceived. The control element may indicate activation of duplication fora bearer. At 3630, in response to receiving the control element, a firstplurality of resources and a second plurality of resources may beactivated. The first plurality of resources may correspond to the firstperiodic resource allocation on a first cell. The second plurality ofresources may correspond to the second periodic resource allocation on asecond cell. First packets of the bearer may be transmitted via thefirst plurality of resources. A duplicate of the first packets may betransmitted via the second plurality of resources.

According to an embodiment, the duplication may be packet dataconvergence protocol duplication. According to an embodiment, the bearermay be a data radio bearer. According to an embodiment, the bearer maycorrespond to a first logical channel and a second logical channel.According to an embodiment, a first buffer associated with the firstlogical channel may comprise the first packets; and a second bufferassociated with the second logical channel may comprise the duplicate ofthe first packets. According to an embodiment, the control element maybe a medium access control (MAC) control element.

In this specification, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” In this specification,the term “may” is to be interpreted as “may, for example.” In otherwords, the term “may” is indicative that the phrase following the term“may” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.If A and B are sets and every element of A is also an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}.

In this specification, parameters (Information elements: IEs) maycomprise one or more objects, and each of those objects may comprise oneor more other objects. For example, if parameter (IE) N comprisesparameter (IE) M, and parameter (IE) M comprises parameter (IE) K, andparameter (IE) K comprises parameter (information element) J, then, forexample, N comprises K, and N comprises J. In an example embodiment,when one or more messages comprise a plurality of parameters, it impliesthat a parameter in the plurality of parameters is in at least one ofthe one or more messages, but does not have to be in each of the one ormore messages.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an isolatableelement that performs a defined function and has a defined interface toother elements. The modules described in this disclosure may beimplemented in hardware, software in combination with hardware,firmware, wetware (i.e hardware with a biological element) or acombination thereof, all of which are behaviorally equivalent. Forexample, modules may be implemented as a software routine written in acomputer language configured to be executed by a hardware machine (suchas C, C++, Fortran, Java, Basic, Matlab or the like) or amodeling/simulation program such as Simulink, Stateflow, GNU Octave, orLabVIEWMathScript. Additionally, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers and microprocessors are programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDsare often programmed using hardware description languages (HDL) such asVHSIC hardware description language (VHDL) or Verilog that configureconnections between internal hardware modules with lesser functionalityon a programmable device. Finally, it needs to be emphasized that theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the spirit and scope. In fact, after reading theabove description, it will be apparent to one skilled in the relevantart(s) how to implement alternative embodiments. Thus, the presentembodiments should not be limited by any of the above describedexemplary embodiments. In particular, it should be noted that, forexample purposes, the above explanation has focused on the example(s)using FDD communication systems. However, one skilled in the art willrecognize that embodiments of the invention may also be implemented in asystem comprising one or more TDD cells (e.g. frame structure 2 and/orframe structure 3-licensed assisted access). The disclosed methods andsystems may be implemented in wireless or wireline systems. The featuresof various embodiments presented in this invention may be combined. Oneor many features (method or system) of one embodiment may be implementedin other embodiments. Only a limited number of example combinations areshown to indicate to one skilled in the art the possibility of featuresthat may be combined in various embodiments to create enhancedtransmission and reception systems and methods.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112, paragraph 6. Claims that do not expressly include the phrase“means for” or “step for” are not to be interpreted under 35 U.S.C. 112.

What is claimed is:
 1. A method comprising: receiving, by a wirelessdevice, one or more messages comprising configuration parametersindicating a plurality of data bearers comprising one or more first databearers configured with packet data convergence protocol (PDCP)duplication and one or more second data bearers that are not configuredwith PDCP duplication, wherein each data bearer in the plurality of databearers is identified by a data bearer identifier; receiving a controlelement of a fixed size of one octet, wherein: the control elementcomprises a sequence of activation bits comprising a first activationbit for a first data bearer in the one or more first data bearers,wherein a first position of the first activation bit in the one octetidentifies a second position of a first data bearer identifier in anordered list of data bearer identifiers of the one or more first databearers configured with the PDCP duplication, wherein the ordered listof data bearer identifiers excludes the one or more second data bearsthat are not configured with PDCP duplication; and a first value of thefirst activation bit indicates whether the PDCP duplication for thefirst data bearer is activated or deactivated; and transmitting, inresponse to the control element indicating that the PDCP duplication isactivated for the first data bearer, a first packet corresponding to thefirst data bearer via a first cell and a duplicate of the first packetvia a second cell different from the first cell.
 2. The method of claim1, wherein: a first buffer associated with a first logical channelcomprises the first packet; and a second buffer associated with a secondlogical channel comprises the duplicate of the first packet.
 3. Themethod of claim 2, wherein the one or messages indicates that: the firstcell is a first allowed serving cell for transmission of data from thefirst logical channel; and the second cell is a second allowed servingcell for transmission of data from the second logical channel.
 4. Themethod of claim 2, wherein the one or messages indicates that: a firstplurality of cells are first allowed serving cells for transmission ofdata from the first logical channel, the first plurality of cellscomprising the first cell; and a second plurality of cells are secondallowed serving cells for transmission of data from the second logicalchannel, the second plurality of cells comprising the second cell. 5.The method of claim 1, wherein: the first packet corresponds to a firstradio link control (RLC) entity and a first logical channel; and theduplicate of the first packet corresponds to a second RLC entity and asecond logical channel.
 6. The method of claim 1, further comprising:receiving a first uplink grant for transmission of the first packet viathe first cell; and receiving a second uplink grant for transmission ofthe duplicate of the first packet via the second cell.
 7. The method ofclaim 1, wherein the ordered list is an ascending ordered list.
 8. Themethod of claim 1, wherein the ordered list is a descending orderedlist.
 9. The method of claim 1, wherein the first position is same asthe second position.
 10. The method of claim 1, wherein the controlelement indicates: activation of the PDCP duplication for the first databearer in response to the first value being one; and deactivation of thePDCP duplication for the first data bearer in response to the firstvalue being zero.
 11. The method of claim 1, wherein a data bearer inthe plurality of data bearers is a data radio bearer.
 12. The method ofclaim 1, wherein the control element is associated with a logicalchannel identifier indicating that the control element is for PDCPduplication activation/deactivation of one or more data bearers.
 13. Themethod of claim 1, further comprising: receiving a second controlelement indicating that the PDCP duplication is deactivated for thefirst data bearer; receiving an uplink grant for the second cell; andtransmitting a packet associated with the first data bearer based on theuplink grant.
 14. The method of claim 3, wherein: the first packetcorresponds to a first radio link control (RLC) entity and the firstlogical channel; and the duplicate of the first packet corresponds to asecond RLC entity and the second logical channel.
 15. The method ofclaim 13, further comprising: receiving a first uplink grant fortransmission of the first packet via the first cell; and receiving asecond uplink grant for transmission of the duplicate of the firstpacket via the second cell.
 16. The method of claim 14, wherein thefirst position is same as the second position.
 17. The method of claim15, wherein the ordered list is an ascending ordered list.
 18. Themethod of claim 15, wherein the ordered list is a descending orderedlist.
 19. The method of claim 4, wherein: the first packet correspondsto a first radio link control (RLC) entity and the first logicalchannel; and the duplicate of the first packet corresponds to a secondRLC entity and the second logical channel.
 20. The method of claim 19,further comprising: receiving a first uplink grant for transmission ofthe first packet via the first cell; and receiving a second uplink grantfor transmission of the duplicate of the first packet via the secondcell.